Suresh,
I just opened this Jira issue:
https://issues.apache.org/jira/browse/LUCENE-1168
and attached a patch that fixes the issue.
If possible, can you confirm that it fixes your issue? Thanks for
discovering & raising this!
Mike
On Feb 7, 2008, at 6:18 AM, suresh guvvala wrote:
I think, I have a test case to reproduce java.io.IOException: read
past EOF execption while merging. The attached code generates this
exception upon executing it.
Suresh.
On 12/19/07, Michael McCandless <[EMAIL PROTECTED]> wrote:
Grant Ingersoll wrote:
> The field that is causing the problem in the stack trace is neither
> binary nor compressed, nor is it even stored.
This would also be possible with the one bug I found on hitting an
exception in DocumentsWriter.addDocument.
Basically the bug can cause only a subset of the stored fields to be
added to the fdt file even though the vint header claimed more stored
fields were written. Grant, you're really sure you saw no exception
in Solr's logs right? Note that the exception would corrupt the
index but would then not be detected until that corrupted segment
gets merged, so it could have been in an earlier batch of added docs,
for example.
I've been testing various combinations of changing schema, turning on/
off stored for the same field, interested deletions, empty stored
fields, etc, and can't otherwise get the bug to come out. It's a
sneaky one!
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<TestCase.java>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
