OK I have a small test case showing the issue!
I opened https://issues.apache.org/jira/browse/LUCENE-7491
Thanks for reporting this, Hans.
Mike McCandless
http://blog.mikemccandless.com
On Tue, Oct 11, 2016 at 12:08 PM, Hans Lund wrote:
> hmm you're right - when it revealed a bug in our index
hmm you're right - when it revealed a bug in our indexing code I stopped
wondering ;-) but now I tried to create small tests to show the behavior -
until now without success. I'm pretty sure that I can reproduce it by
re-introducing our index bug, unfortunately it occurs after some hours
parsing an
Hmm, that should be "OK" from Lucene's standpoint.
I mean, it should not result in strange merge exceptions later on.
I think there's a bug somewhere in Lucene's efforts to pretend it's
fully schema-less ... I'll try to reproduce this.
Mike McCandless
http://blog.mikemccandless.com
On Tue, Oct
Turned out to be must much simpler - we had added a new 'dynamic' field to
a stats doc a count on articles based on identified language code. Having a
set of test documents in German, English, Swedish - no one had suspected
the obvious that the language detection categorized a single document as
be
It looks like the field infos of your index went out of sync with data
stored in the files about points.
Can you run CheckIndex on your index (potentially with the `-fast` option
so that it only verifies checksums)? It could be that one of these two
parts of the index got corrupted.
Since you wer
