In a past life, Lucene (1.2, I believe) could be tricked into this behavior if an ill-behaved app added fields with embedded \0's in their value property. If I recall, the \0 could end up being written in the term data and corrupting the index for future readers. It was awhile ago - apologies if this turns out to be a red herring.
-----Original Message----- From: Victor Hadianto [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2003 4:16 PM To: Lucene Users List Subject: Re: Term out of order. > Apparently so :( > http://www.google.com/search?q=lucene+%22term+out+of+order%22 Eeek .. so does anyone know what happen here? /victor > > Otis > > --- Victor Hadianto <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > I'm using Lucene.Net but seems appropriate to post here as well. I > > have been getting this exception "Term out of order" every now and > > then while doing a > > bulk indexing. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
