lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rafał Kuć <>
Subject Re: understanding the need to reindex a document
Date Mon, 22 Oct 2012 19:56:00 GMT

This is because how the Lucene inverted index works and the amount of
changes that would have to be done. However there is a work in
progress issue -
There is some technical information there, so you may want to check

 Rafał Kuć
 Sematext :: :: Solr - Lucene - Nutch

> I can understand that (i.e. why in place wont work), but the Q would be,
> why one can't read in a document, add() or removeField() that document
> and then updateDocument() that document.

> On 10/22/2012 03:43 PM, Apostolis Xekoukoulotakis wrote:
>> I am not that familiar with Lucene, so my answer may be a bit off.
>> Search on the internet about log structured storage. There you will find
>> why rewriting an entry is better than updating an existing entry.
>> Leveldb/cassandra/bigTable use it. maybe search these terms as well.
>> 2012/10/22 Shaya Potter <>
>>> so there are lots of Qs that are asked about wanting to modify a lucene
>>> document (i.e. remove fields, add fields....) but are told that one needs
>>> to reindex.
>>> No one ever answers the technical Q of why this is, and I'm interested in
>>> that.  presumambly because documents aren't stored as documents or even in
>>> any form that could be reassembled into a document, but I'm interested in
>>> what the actual answer is.
>>> thanks.
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: java-user-unsubscribe@lucene.**<>
>>> For additional commands, e-mail: java-user-help@lucene.apache.**org<>

> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message