OK, phew! Thanks for bringing closure.
Mike
Micah Jaffe wrote:
Hi, thanks for responding. A quick follow-up, the problem turned
out to be more complex than originally explained, and it was not in
fact a problem with buggy behavior in Lucene. A static nested class
created a fugly point
Hi, thanks for responding. A quick follow-up, the problem turned out
to be more complex than originally explained, and it was not in fact a
problem with buggy behavior in Lucene. A static nested class created
a fugly point where I was holding/using the wrong reader at the time
of failure.
IndexReader.open opens the latest segments_N file. If that file
references only 1 segment, a SegmentReader is returned, else a
MultiSegmentReader.
I'm confused why you see the SegmentReader impl giving too few results
-- that should only be returned if your index legitimately has only 1
My environment:
Lucene 2.3.2 on Linux, Java 1.6.0_07-b06, running under Tomcat 5.5.26
What I'm trying to do seems pretty simple, but is causing a headache
which I can't sleuth out. When I try to build an IndexSearcher using
an IndexReader, the IndexReader.open( String_to_index_dir ) call
