P.S. At one point I tried doing an in-memory index using the
RAMDirectory
and then merging it with an on-disk index and it didn't work. The
RAMDirectory never flushed to disk... leaving me with an
empty index. I
think this is because of a bug in the mechanism that is
supposed
Thanks for the detailed information, Doug! That helps a lot.
Based on what you've said and on taking a closer look at the code, it looks
like by setting mergeFactor and maxMergeDocs to Integer.MAX_VALUE, an entire
index will be built in a single segment completely in memory (using the
From: Scott Ganyo [mailto:[EMAIL PROTECTED]]
Thanks for the detailed information, Doug! That helps a lot.
Based on what you've said and on taking a closer look at the
code, it looks
like by setting mergeFactor and maxMergeDocs to
Integer.MAX_VALUE, an entire
index will be built in a
From: Scott Ganyo [mailto:[EMAIL PROTECTED]]
We're having a heck of a time with too many file handles
around here. When
we create large indexes, we often get thousands of temporary
files in a given index!
Thousands, eh? That seems high.
The maximum number of segments should be
