RE: MultiFieldQueryParser on integer and string (8.6.0)

For LongPoint field, you need to use methods that returns Query in LongPoint class. static Query

Re: MultiFieldQueryParser on integer and string (8.6.0)

I think you will need to subclass MultiFieldQueryParser so that the proper Query is created when the field is the numeric one. Maybe overriding createFieldQuery(). El 8/10/20 a las 11:48, Stephane Passignat escribió: Hi, I'm trying to index numeric, and then to query them using java api and lu

Re: Lucene 8.7 error searching an index created with 8.3

This is reproducible only within our product, I haven't yet been able to isolate this and reproduce it standalone. It's Java 11. Yes, I've run CheckIndex with the "-slow" option and with assertions enabled. El 24/11/20 a las 11:32, Adrien Grand escribió: This is related to phrase matching ind

Re: Lucene 8.7 error searching an index created with 8.3

This is related to phrase matching indeed. Positions are stored in blocks of 128 values, where every block is encoded with a different number of bits per value. And the error you are seeing suggests that one block reports 69 bits per value. The fact that CheckIndex didn't complain is surprising. D

Re: Lucene 8.7 error searching an index created with 8.3

Lucene 8.7's CheckIndex says there are no errors in the index. On closer inspection this seems related to phrase matching... El 24/11/20 a las 05:18, Adrien Grand escribió: Can you run CheckIndex on your index to make sure it is not corrupt? On Tue, Nov 24, 2020 at 1:01 AM Nicolás Lichtmaier

Re: Lucene 8.7 error searching an index created with 8.3

Can you run CheckIndex on your index to make sure it is not corrupt? On Tue, Nov 24, 2020 at 1:01 AM Nicolás Lichtmaier wrote: > I'm seeing errors like this one (using backwards codecs): > > java.lang.ArrayIndexOutOfBoundsException: Index 69 out of bounds for > length 33 > at > org.apache.l