lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson" <erickerick...@gmail.com>
Subject Re: What are the best document edit options?
Date Wed, 17 Dec 2008 18:22:30 GMT
I'll leave those details to the experts who are up to speed <G>.

On Wed, Dec 17, 2008 at 11:52 AM, Thomas J. Buhr <visual.logic@gmail.com>wrote:

> Erick,
>
> Thanks for the good news, my question was still lingering from months ago
> when I initially looked at an older Lucene.
>
> Now I need a bit more specific info, since much in my architecture rests on
> this ability to modify document fields dynamically. Where can I see how
> IndexWriter.updateDocument works without getting into Lucene all over again
> until this important issue is resolved? Is there a sample of its usage for
> updating specific fields in a given document? Is the update immediate or
> delayed?
>
> Thanks, Thom
>
>
>
> On 17-Dec-08, at 8:15 AM, Erick Erickson wrote:
>
>  What version of Lucene are you using? The more recent ones have
>> IndexWriter.updateDocument......
>>
>> Best
>> Erick
>>
>> On Wed, Dec 17, 2008 at 2:20 AM, Thomas J. Buhr <visual.logic@gmail.com
>> >wrote:
>>
>>  Hello Lucene,
>>>
>>> Looking at the document object it seems like each time I want to edit its
>>> contents I need to do the following:
>>>
>>> 1 - fetch the document
>>> 2 - dump its contents into a temp container
>>> 3 - update field values in the temp container
>>> 4 - create a new document
>>> 5 - transfer my updated field values back into the new document
>>> 6 - add document back into the index
>>>
>>> This seems like a long process, is it really necessary?
>>>
>>> An index structure does seem ideal for storing and searching a large set
>>> of
>>> symbolic strings in my app. From here I need to render these string chars
>>> as
>>> visible nodes on screen, this can be done with the new JavaFX API .
>>>
>>> JavaFX has a unique binding system that would also be great to use. Using
>>> binding I could setup two way (inverse) binding between the fields in a
>>> document and the rendered screen nodes. This way when there is a value
>>> change in the rendered node the document field values  would auto update
>>> and
>>> also if there is a change in the document field value the node would auto
>>> update.
>>>
>>> This update senario via binding would be ideal. How can it be done?
>>>
>>> Information about the JavaFX binding mechanism is available at this link:
>>>
>>> http://java.sun.com/javafx/1/tutorials/core/dataBinding
>>>
>>>
>>> Hope this can work,
>>>
>>> Thom
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: java-user-help@lucene.apache.org
>>>
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message