Re: A flush exception in lucene 4.10.0

The exception in my case is related to one index field. The field is string type, indexed, tokenized and stored, index option is docsAndFreqsAndPositionsAndOffsets. Each doc may index this field more than one times. For example doc 0 may index it 3 times, 1st value is "A B C", 2nd is "D E F"，3rd

Re: A flush exception in lucene 4.10.0

My version is 4.10.0 which is later than 4.5, but I didn't find the fix like https://issues.apache.org/jira/secure/attachment/12593180/LUCENE-5116.patch in indexwriter, neither in 4.10.4. Not sure which version has fixed it. public void addIndexes(IndexReader... readers) throws IOException {

Re: A flush exception in lucene 4.10.0

Maybe (though it was committed in Lucene 4.5)? Robert Muir pointed to this issue as fixing , which contains a similar stack track to yours. -- Steve www.lucidworks.com > On Mar 9, 2017, at 6:

Re: A flush exception in lucene 4.10.0

This seems likely to be a Lucene bug, and it seems vaguely familiar. I tried to find the issue / commit that may have fixed it, but so far failed. But 4.10.0 is truly ancient; you should at least try upgrading to 4.10.4? Mike McCandless http://blog.mikemccandless.com On Wed, Mar 8, 2017 at 6:1

Re: A flush exception in lucene 4.10.0

Seems it is related to an empty segment, all docs in this segment are deleted before commit. Any one can confirm it? Maybe I need upgrade my lucene version. 2017-03-03 10:19 GMT+08:00 Yonghui Zhao : > Hi all, > > Anyone see this exception before? Is it a lucene bug or something wrong > in my co

A flush exception in lucene 4.10.0

Hi all, Anyone see this exception before? Is it a lucene bug or something wrong in my code? Exception in thread "Thread-14" java.lang.IllegalArgumentException: maxValue must be non-negative (got: -1) at org.apache.lucene.util.packed.PackedInts.bitsRequired(PackedInts.java:1141)