> read each document from the db
> add the field
> search lucene based on the UID
> remove document from lucene based on UID
> build new lucene document that has only indexed fields and the UID
> add lucene document
>
> There are some newer Lucene 2+ features that might make this process
> faster,
We have a 'reindex' process for this that works like this:
read each document from the db
add the field
search lucene based on the UID
remove document from lucene based on UID
build new lucene document that has only indexed fields and the UID
add lucene document
There are some newer Lucene 2+ fe
Many thanks for you answer - sorry i didn't come around to ask
earlier, but that brings me to a new question: What if I do(!) need to
append a field that needs to be indexed?
On 3/20/07, robert engels <[EMAIL PROTECTED]> wrote:
If you have "unique ids" available to you, I think the best solution
If you have "unique ids" available to you, I think the best solution
to accomplish a lot of this would be to use a very simple embedded db
to store the documents (we use a version of JDBM). Just store the key
as a stored field in the Lucene document, and the document in JDBM.
This has the a
As for now, when ever the index of a document needs to be updated, the
complete document needs to be deleted, then newly indexed & finally
added to the index repository. If, however, information merely needed
to be added to the existing document (->appended), the described
procedure creates a grea
