Thanks. Yes what you said is correct. There were two bugs, one in the
patch and a few in Ocean since fixed.
On Fri, Jul 11, 2008 at 7:49 PM, Michael McCandless <
[EMAIL PROTECTED]> wrote:
>
> I think if your SegmentReader is not returning the right result when
> numDocs() is called it can lead
I think if your SegmentReader is not returning the right result when
numDocs() is called it can lead to this.
Eg if your maxDoc() is 1000 and you think you have 100 deleted docs
(so numDocs() returns 900) but upon iterating through the docs you
only saw say 50 that were deleted, then, whe
Periodically seeing this exception when testing out Ocean. What would be a
possible cause for this? I assume it is a problem in the index. The code
is merging custom segmentreaders that are created using
http://issues.apache.org/jira/browse/LUCENE-1314 IndexReader.clone. I need
to isolate if it
