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 added benefit that merges are much faster with large
documents), since there is no-rewriting/copying of document data
during a merge.
This solution also makes append" trivial, unless you are appending
fields that need to be indexed.
On Mar 20, 2007, at 12:11 PM, Alexander Kern wrote:
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 great overhead. Up to now Lucene does not provide
an 'append' function.
My question is: Is an 'append' function (or something similar) planned
for future releases, and if not, which classes would be most suitable
for such a function (and contain the functions needed to support such
a function) if I would want to edit the source to fit my needs.
Many thanks in advance - Alexander
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
