ave an external source for all non-stored
fields, or at least non-stored fields which are not copied from another
field which is stored.
-- Jack Krupansky
-Original Message-
From: Shaya Potter
Sent: Monday, October 22, 2012 3:47 PM
To: java-user@lucene.apache.org
Subject: Re: understand
Hello!
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 - https://issues.apache.org/jira/browse/LUCENE-3837
There is some technical information there, so you may want to check
it.
--
Regards,
Rafa
I cant answer you that. But even if it is feasible, maybe the answer is
that noone really needed it.
2012/10/22 Shaya Potter
> 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 updateDocume
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
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 Pott
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 document
