Just beware, though, that with ParallelReader you must ensure that
the internal docIDs of both indices remain "aligned" over time.
If you never do deletions, then that happens for free.
If you do deletions, then, you must change IndexWriter to buffer by
doc count (same doc count for all writhers), and, you must change the
merge policy to LogDocMergePolicy. You also might need to switch to
SerialMergeScheduler if you ever allow readers to refresh against the
indices while a writer is still open. If you don't do that (ie
reader can only re-open after a writer is closed) then it's safe to
stick with ConcurrentMergeScheduler.
Mike
On Jan 31, 2008, at 4:23 AM, Doron Cohen wrote:
This may help:
http://www.nabble.com/Updating-Lucene-Index-with-Unstored-fields-
tt15188818.html#a15188818
Doron
On Thu, Jan 31, 2008 at 2:42 AM, John Wang <[EMAIL PROTECTED]>
wrote:
Hi all:
We have a large index and it is difficult to reindex.
We want to add another field to the index without reindexing,
e.g. just
create a new inverted index, dictionary files etc.
How feasible is it to add this to lucene?
Thanks
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
