Scott Montgomerie wrote:
> I just tried it with the latest nightly build, the problem still happens.
> 
> I think it must have to do with a corrupted index somehow.   I've also
> noticed, as a separate issue, that after this period of time (4-5 days),
> certain documents aren't indexed correctly.  For example, I will do a query:
> 
> Query for Field 1 with value A returns a list of documents.  In these
> documents is a document with Field 2 with value B.
> Query for Field 2 with value B, return 0 documents.
> 
> Therefore the index on Field 2 is somehow missing certain documents.  Is
> this possible?
> 

Hi Scott,

hmm that doesn't look good. I haven't seen this problem before. Could
you send the index (preferably compressed as .zip) to me (not the
mailing list), please? And your JUnit test that hits this exception, so
that I can debug it?

Thanks for your help!

- Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to