date:20201124

RE: MultiFieldQueryParser on integer and string (8.6.0)

2020-11-24 Thread Karthick Sundaram

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

 


static
 Query

 
 newExactQuery(
 String field, long value)

Create a query for matching an exact long value.


static
 Query

 
 newRangeQuery(
 String field, long[] lowerValue, long[] upperValue)

Create a range query for n-dimensional long values.


static
 Query

 
 newRangeQuery(
 String field, long lowerValue, long upperValue)

Create a range query for long values.


static
 Query

 
 newSetQuery(
 String field,
 Collection<
 Long> values)

Create a query matching any of the specified 1D values.


static
 Query

 
 newSetQuery(
 String field, long... values)

Create a query matching any of the specified 1D values.

 

Regards,

Karthick

 

-Original Message-
From: Nicolás Lichtmaier [mailto:nicol...@wolfram.com.INVALID] 
Sent: Tuesday, November 24, 2020 1:25 PM
To: java-user@lucene.apache.org; Stephane Passignat 
Subject: 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 

> lucene 8.6. I tried several numeric Field types, but I can't make it 

> work.

> Can someone help me to store numeric in the datastore and then to 

> query them ?

> ThanksStéphane

> 

> Here is a simple JUnit test

> package test.data;

> import org.apache.lucene.analysis.standard.StandardAnalyzer;

> import org.apache.lucene.document.*;

> import org.apache.lucene.index.DirectoryReader;

> import org.apache.lucene.index.IndexReader;

> import org.apache.lucene.index.IndexWriter;

> import org.apache.lucene.index.IndexWriterConfig;

> import org.apache.lucene.queryparser.classic.MultiFieldQueryParser;

> import org.apache.lucene.queryparser.classic.ParseException;

> import org.apache.lucene.queryparser.classic.QueryParser;

> import org.apache.lucene.search.IndexSearcher;

> import org.apache.lucene.search.Query; import 

> org.apache.lucene.search.ScoreDoc;

> import org.apache.lucene.search.TopDocs; import 

> org.apache.lucene.store.Directory;

> import org.apache.lucene.store.RAMDirectory;

> import org.junit.Assert;

> import org.junit.BeforeClass;

> import org.junit.Test;

> import org.junit.runner.RunWith;

> import org.junit.runners.Parameterized;

> 

> import java.io.IOException;

> import java.math.BigInteger;

> import java.util.Arrays;

> import java.util.Collection;

> 

> @RunWith(Parameterized.class)

> public class MTest {

> static Directory index = new RAMDirectory();

> private String query;

> 

> public MTest(String query) {

>this.query = query;

> }

> 

> @Parameterized.Parameters(name = "{0}")

> public static Collection data() {

>Object[][]

>  scannedClasses =

>  new Object[][]{{"TextField:Client"},

>  {"LongPoint:17"},

>  {"LongPoint:[16 TO 18]"},

>  {"BigIntegerPoint:21"},

>  {"BigIntegerPoint:[20 TO 22]"},

>  {"StringField:Stephane"},

>  {"Date:20200615"},

>

Re: MultiFieldQueryParser on integer and string (8.6.0)

2020-11-24 Thread Nicolás Lichtmaier

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
lucene 8.6. I tried several numeric Field types, but I can't make it
work.
Can someone help me to store numeric in the datastore and then to
query them ?
ThanksStéphane

Here is a simple JUnit test
package test.data;
import org.apache.lucene.analysis.standard.StandardAnalyzer;
import org.apache.lucene.document.*;
import org.apache.lucene.index.DirectoryReader;
import org.apache.lucene.index.IndexReader;
import org.apache.lucene.index.IndexWriter;
import org.apache.lucene.index.IndexWriterConfig;
import org.apache.lucene.queryparser.classic.MultiFieldQueryParser;
import org.apache.lucene.queryparser.classic.ParseException;
import org.apache.lucene.queryparser.classic.QueryParser;
import org.apache.lucene.search.IndexSearcher;
import org.apache.lucene.search.Query;
import org.apache.lucene.search.ScoreDoc;
import org.apache.lucene.search.TopDocs;
import org.apache.lucene.store.Directory;
import org.apache.lucene.store.RAMDirectory;
import org.junit.Assert;
import org.junit.BeforeClass;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.junit.runners.Parameterized;

import java.io.IOException;
import java.math.BigInteger;
import java.util.Arrays;
import java.util.Collection;

@RunWith(Parameterized.class)
public class MTest {
static Directory index = new RAMDirectory();
private String query;

public MTest(String query) {
   this.query = query;
}

@Parameterized.Parameters(name = "{0}")
public static Collection data() {
   Object[][]
 scannedClasses =
 new Object[][]{{"TextField:Client"},
 {"LongPoint:17"},
 {"LongPoint:[16 TO 18]"},
 {"BigIntegerPoint:21"},
 {"BigIntegerPoint:[20 TO 22]"},
 {"StringField:Stephane"},
 {"Date:20200615"},
 {"Date:[20200614 TO 20200616]"},
 {"DoublePoint:37"},
 {"DoublePoint:[37 TO 38]"},};
   return Arrays.asList(scannedClasses);
}

@BeforeClass
public static void init() throws IOException, ParseException {
   StandardAnalyzer analyzer = new StandardAnalyzer();
   IndexWriterConfig config = new IndexWriterConfig(analyzer);
   config.setOpenMode(IndexWriterConfig.OpenMode.CREATE_OR_APPEND);
   try (IndexWriter writer = new IndexWriter(index, config)) {
  final Document doc = new Document();
  doc.add(new TextField("TextField", "Client",
Field.Store.YES));
  doc.add(new StringField("StringField", "Stephane",
Field.Store.YES));
  doc.add(new LongPoint("LongPoint", 17));
  doc.add(new BigIntegerPoint("BigIntegerPoint", new
BigInteger("21")));
  doc.add(new DoublePoint("DoublePoint", new Double(37.7)));
  doc.add(new StringField("Date", "20200615",
Field.Store.YES));
  writer.addDocument(doc);
  writer.commit();
   }
}

private void query(Directory index, QueryParser
multiFieldQueryParser, String query) throws ParseException,
IOException {
   System.out.println("query = " + query);
   Query q = multiFieldQueryParser.parse(query);
   int hitsPerPage = 10;
   IndexReader reader = DirectoryReader.open(index);
   IndexSearcher searcher = new IndexSearcher(reader);
   TopDocs docs = searcher.search(q, hitsPerPage);
   ScoreDoc[] hits = docs.scoreDocs;
   Assert.assertEquals(query, 1, hits.length);
}

@Test
public void testString() throws IOException, ParseException {
   StandardAnalyzer analyzer = new StandardAnalyzer();
   final QueryParser multiFieldQueryParser = new
MultiFieldQueryParser(new String[]{"longPoint", "Entity"}, analyzer);
   query(index, multiFieldQueryParser, query);
}
}




-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

Re: Lucene 8.7 error searching an index created with 8.3

2020-11-24 Thread Nicolás Lichtmaier

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 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. Did you only 
verify checksums (the -fast option) or did you run the full CheckIndex?


Is your problem reproducible? If yes, does it still reproduce if you 
move to a recent JVM?


On Tue, Nov 24, 2020 at 3:22 PM Nicolás Lichtmaier 
mailto:nicol...@wolfram.com>> wrote:


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
>  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.lucene.codecs.lucene50.ForUtil.readBlock(ForUtil.java:196)
>>       at
>>
>>

org.apache.lucene.codecs.lucene50.Lucene50PostingsReader$EverythingEnum.refillPositions(Lucene50PostingsReader.java:721)
>>       at
>>
>>

org.apache.lucene.codecs.lucene50.Lucene50PostingsReader$EverythingEnum.nextPosition(Lucene50PostingsReader.java:924)
>>       at
>>
>>

org.apache.lucene.search.PhrasePositions.nextPosition(PhrasePositions.java:57)
>>       at
>>
>>

org.apache.lucene.search.SloppyPhraseMatcher.advancePP(SloppyPhraseMatcher.java:262)
>>       at
>>
>>

org.apache.lucene.search.SloppyPhraseMatcher.nextMatch(SloppyPhraseMatcher.java:173)
>>       at
>>
org.apache.lucene.search.PhraseScorer$1.matches(PhraseScorer.java:58)
>>       at
>>
>>

org.apache.lucene.search.DoubleValuesSource$WeightDoubleValuesSource$1.advanceExact(DoubleValuesSource.java:631)
>>       at
>>
>>

org.apache.lucene.queries.function.FunctionScoreQuery$QueryBoostValuesSource$1.advanceExact(FunctionScoreQuery.java:343)
>>       at
>>
org.apache.lucene.search.DoubleValues$1.advanceExact(DoubleValues.java:53)
>>       at
>>
org.apache.lucene.search.DoubleValues$1.advanceExact(DoubleValues.java:53)
>>       at
>>
>>

org.apache.lucene.queries.function.FunctionScoreQuery$MultiplicativeBoostValuesSource$1.advanceExact(FunctionScoreQuery.java:270)
>>       at
>>
>>

org.apache.lucene.queries.function.FunctionScoreQuery$FunctionScoreWeight$1.score(FunctionScoreQuery.java:228)
>>       at
>>
>>

org.apache.lucene.search.DisjunctionMaxScorer.score(DisjunctionMaxScorer.java:67)
>>       at
>>
>>
org.apache.lucene.search.DisjunctionScorer.score(DisjunctionScorer.java:194)
>>       at
>>
>>

org.apache.lucene.search.DoubleValuesSource$2.doubleValue(DoubleValuesSource.java:344)
>>       at
>>
>>

org.apache.lucene.queries.function.FunctionScoreQuery$MultiplicativeBoostValuesSource$1.doubleValue(FunctionScoreQuery.java:265)
>>       at
>>
>>

org.apache.lucene.queries.function.FunctionScoreQuery$FunctionScoreWeight$1.score(FunctionScoreQuery.java:229)
>>       at
>>
>>

org.apache.lucene.search.TopScoreDocCollector$SimpleTopScoreDocCollector$1.collect(TopScoreDocCollector.java:76)
>>       at
>>
org.apache.lucene.search.Weight$DefaultBulkScorer.scoreAll(Weight.java:276)
>>       at
>>
org.apache.lucene.search.Weight$DefaultBulkScorer.score(Weight.java:232)
>>       at
org.apache.lucene.search.BulkScorer.score(BulkScorer.java:39)
>>       at
>>
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:661)
>>       at
>>
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:445)
>>       at
>>
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:574)
>>       at
>>
org.apache.lucene.search.IndexSearcher.searchAfter(IndexSearcher.java:421)
>>       at
>>
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:432)
>>
>> They seem to be connected with double values stored as
"docvalues" and
>> user in formulas to affect the scores.
>>
>> Is there any known incompatibility? Is this something that
should work?
>> Must I rebuild the indices with 8.7? (that would be bad for our
usecase
>> here)
>>
>> Thanks!
>>
>>
>>

Re: Lucene 8.7 error searching an index created with 8.3

2020-11-24 Thread Adrien Grand

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. Did you only verify
checksums (the -fast option) or did you run the full CheckIndex?

Is your problem reproducible? If yes, does it still reproduce if you move
to a recent JVM?

On Tue, Nov 24, 2020 at 3:22 PM Nicolás Lichtmaier 
wrote:

> 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
> >  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.lucene.codecs.lucene50.ForUtil.readBlock(ForUtil.java:196)
> >>   at
> >>
> >>
> org.apache.lucene.codecs.lucene50.Lucene50PostingsReader$EverythingEnum.refillPositions(Lucene50PostingsReader.java:721)
> >>   at
> >>
> >>
> org.apache.lucene.codecs.lucene50.Lucene50PostingsReader$EverythingEnum.nextPosition(Lucene50PostingsReader.java:924)
> >>   at
> >>
> >>
> org.apache.lucene.search.PhrasePositions.nextPosition(PhrasePositions.java:57)
> >>   at
> >>
> >>
> org.apache.lucene.search.SloppyPhraseMatcher.advancePP(SloppyPhraseMatcher.java:262)
> >>   at
> >>
> >>
> org.apache.lucene.search.SloppyPhraseMatcher.nextMatch(SloppyPhraseMatcher.java:173)
> >>   at
> >> org.apache.lucene.search.PhraseScorer$1.matches(PhraseScorer.java:58)
> >>   at
> >>
> >>
> org.apache.lucene.search.DoubleValuesSource$WeightDoubleValuesSource$1.advanceExact(DoubleValuesSource.java:631)
> >>   at
> >>
> >>
> org.apache.lucene.queries.function.FunctionScoreQuery$QueryBoostValuesSource$1.advanceExact(FunctionScoreQuery.java:343)
> >>   at
> >>
> org.apache.lucene.search.DoubleValues$1.advanceExact(DoubleValues.java:53)
> >>   at
> >>
> org.apache.lucene.search.DoubleValues$1.advanceExact(DoubleValues.java:53)
> >>   at
> >>
> >>
> org.apache.lucene.queries.function.FunctionScoreQuery$MultiplicativeBoostValuesSource$1.advanceExact(FunctionScoreQuery.java:270)
> >>   at
> >>
> >>
> org.apache.lucene.queries.function.FunctionScoreQuery$FunctionScoreWeight$1.score(FunctionScoreQuery.java:228)
> >>   at
> >>
> >>
> org.apache.lucene.search.DisjunctionMaxScorer.score(DisjunctionMaxScorer.java:67)
> >>   at
> >>
> >>
> org.apache.lucene.search.DisjunctionScorer.score(DisjunctionScorer.java:194)
> >>   at
> >>
> >>
> org.apache.lucene.search.DoubleValuesSource$2.doubleValue(DoubleValuesSource.java:344)
> >>   at
> >>
> >>
> org.apache.lucene.queries.function.FunctionScoreQuery$MultiplicativeBoostValuesSource$1.doubleValue(FunctionScoreQuery.java:265)
> >>   at
> >>
> >>
> org.apache.lucene.queries.function.FunctionScoreQuery$FunctionScoreWeight$1.score(FunctionScoreQuery.java:229)
> >>   at
> >>
> >>
> org.apache.lucene.search.TopScoreDocCollector$SimpleTopScoreDocCollector$1.collect(TopScoreDocCollector.java:76)
> >>   at
> >>
> org.apache.lucene.search.Weight$DefaultBulkScorer.scoreAll(Weight.java:276)
> >>   at
> >> org.apache.lucene.search.Weight$DefaultBulkScorer.score(Weight.java:232)
> >>   at org.apache.lucene.search.BulkScorer.score(BulkScorer.java:39)
> >>   at
> >> org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:661)
> >>   at
> >> org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:445)
> >>   at
> >> org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:574)
> >>   at
> >>
> org.apache.lucene.search.IndexSearcher.searchAfter(IndexSearcher.java:421)
> >>   at
> >> org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:432)
> >>
> >> They seem to be connected with double values stored as "docvalues" and
> >> user in formulas to affect the scores.
> >>
> >> Is there any known incompatibility? Is this something that should work?
> >> Must I rebuild the indices with 8.7? (that would be bad for our usecase
> >> here)
> >>
> >> Thanks!
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> >> For additional commands, e-mail: java-user-h...@lucene.apache.org
> >>
> >>
>


-- 
Adrien

Re: Lucene 8.7 error searching an index created with 8.3

2020-11-24 Thread Nicolás Lichtmaier


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
 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.lucene.codecs.lucene50.ForUtil.readBlock(ForUtil.java:196)
  at

org.apache.lucene.codecs.lucene50.Lucene50PostingsReader$EverythingEnum.refillPositions(Lucene50PostingsReader.java:721)
  at

org.apache.lucene.codecs.lucene50.Lucene50PostingsReader$EverythingEnum.nextPosition(Lucene50PostingsReader.java:924)
  at

org.apache.lucene.search.PhrasePositions.nextPosition(PhrasePositions.java:57)
  at

org.apache.lucene.search.SloppyPhraseMatcher.advancePP(SloppyPhraseMatcher.java:262)
  at

org.apache.lucene.search.SloppyPhraseMatcher.nextMatch(SloppyPhraseMatcher.java:173)
  at
org.apache.lucene.search.PhraseScorer$1.matches(PhraseScorer.java:58)
  at

org.apache.lucene.search.DoubleValuesSource$WeightDoubleValuesSource$1.advanceExact(DoubleValuesSource.java:631)
  at

org.apache.lucene.queries.function.FunctionScoreQuery$QueryBoostValuesSource$1.advanceExact(FunctionScoreQuery.java:343)
  at
org.apache.lucene.search.DoubleValues$1.advanceExact(DoubleValues.java:53)
  at
org.apache.lucene.search.DoubleValues$1.advanceExact(DoubleValues.java:53)
  at

org.apache.lucene.queries.function.FunctionScoreQuery$MultiplicativeBoostValuesSource$1.advanceExact(FunctionScoreQuery.java:270)
  at

org.apache.lucene.queries.function.FunctionScoreQuery$FunctionScoreWeight$1.score(FunctionScoreQuery.java:228)
  at

org.apache.lucene.search.DisjunctionMaxScorer.score(DisjunctionMaxScorer.java:67)
  at

org.apache.lucene.search.DisjunctionScorer.score(DisjunctionScorer.java:194)
  at

org.apache.lucene.search.DoubleValuesSource$2.doubleValue(DoubleValuesSource.java:344)
  at

org.apache.lucene.queries.function.FunctionScoreQuery$MultiplicativeBoostValuesSource$1.doubleValue(FunctionScoreQuery.java:265)
  at

org.apache.lucene.queries.function.FunctionScoreQuery$FunctionScoreWeight$1.score(FunctionScoreQuery.java:229)
  at

org.apache.lucene.search.TopScoreDocCollector$SimpleTopScoreDocCollector$1.collect(TopScoreDocCollector.java:76)
  at
org.apache.lucene.search.Weight$DefaultBulkScorer.scoreAll(Weight.java:276)
  at
org.apache.lucene.search.Weight$DefaultBulkScorer.score(Weight.java:232)
  at org.apache.lucene.search.BulkScorer.score(BulkScorer.java:39)
  at
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:661)
  at
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:445)
  at
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:574)
  at
org.apache.lucene.search.IndexSearcher.searchAfter(IndexSearcher.java:421)
  at
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:432)

They seem to be connected with double values stored as "docvalues" and
user in formulas to affect the scores.

Is there any known incompatibility? Is this something that should work?
Must I rebuild the indices with 8.7? (that would be bad for our usecase
here)

Thanks!


-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org




-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

Re: Lucene 8.7 error searching an index created with 8.3

2020-11-24 Thread Adrien Grand

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.lucene.codecs.lucene50.ForUtil.readBlock(ForUtil.java:196)
>  at
>
> org.apache.lucene.codecs.lucene50.Lucene50PostingsReader$EverythingEnum.refillPositions(Lucene50PostingsReader.java:721)
>  at
>
> org.apache.lucene.codecs.lucene50.Lucene50PostingsReader$EverythingEnum.nextPosition(Lucene50PostingsReader.java:924)
>  at
>
> org.apache.lucene.search.PhrasePositions.nextPosition(PhrasePositions.java:57)
>  at
>
> org.apache.lucene.search.SloppyPhraseMatcher.advancePP(SloppyPhraseMatcher.java:262)
>  at
>
> org.apache.lucene.search.SloppyPhraseMatcher.nextMatch(SloppyPhraseMatcher.java:173)
>  at
> org.apache.lucene.search.PhraseScorer$1.matches(PhraseScorer.java:58)
>  at
>
> org.apache.lucene.search.DoubleValuesSource$WeightDoubleValuesSource$1.advanceExact(DoubleValuesSource.java:631)
>  at
>
> org.apache.lucene.queries.function.FunctionScoreQuery$QueryBoostValuesSource$1.advanceExact(FunctionScoreQuery.java:343)
>  at
> org.apache.lucene.search.DoubleValues$1.advanceExact(DoubleValues.java:53)
>  at
> org.apache.lucene.search.DoubleValues$1.advanceExact(DoubleValues.java:53)
>  at
>
> org.apache.lucene.queries.function.FunctionScoreQuery$MultiplicativeBoostValuesSource$1.advanceExact(FunctionScoreQuery.java:270)
>  at
>
> org.apache.lucene.queries.function.FunctionScoreQuery$FunctionScoreWeight$1.score(FunctionScoreQuery.java:228)
>  at
>
> org.apache.lucene.search.DisjunctionMaxScorer.score(DisjunctionMaxScorer.java:67)
>  at
>
> org.apache.lucene.search.DisjunctionScorer.score(DisjunctionScorer.java:194)
>  at
>
> org.apache.lucene.search.DoubleValuesSource$2.doubleValue(DoubleValuesSource.java:344)
>  at
>
> org.apache.lucene.queries.function.FunctionScoreQuery$MultiplicativeBoostValuesSource$1.doubleValue(FunctionScoreQuery.java:265)
>  at
>
> org.apache.lucene.queries.function.FunctionScoreQuery$FunctionScoreWeight$1.score(FunctionScoreQuery.java:229)
>  at
>
> org.apache.lucene.search.TopScoreDocCollector$SimpleTopScoreDocCollector$1.collect(TopScoreDocCollector.java:76)
>  at
> org.apache.lucene.search.Weight$DefaultBulkScorer.scoreAll(Weight.java:276)
>  at
> org.apache.lucene.search.Weight$DefaultBulkScorer.score(Weight.java:232)
>  at org.apache.lucene.search.BulkScorer.score(BulkScorer.java:39)
>  at
> org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:661)
>  at
> org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:445)
>  at
> org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:574)
>  at
> org.apache.lucene.search.IndexSearcher.searchAfter(IndexSearcher.java:421)
>  at
> org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:432)
>
> They seem to be connected with double values stored as "docvalues" and
> user in formulas to affect the scores.
>
> Is there any known incompatibility? Is this something that should work?
> Must I rebuild the indices with 8.7? (that would be bad for our usecase
> here)
>
> Thanks!
>
>
> -
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org
>
>

-- 
Adrien

RE: MultiFieldQueryParser on integer and string (8.6.0)

Re: MultiFieldQueryParser on integer and string (8.6.0)

Re: Lucene 8.7 error searching an index created with 8.3

Re: Lucene 8.7 error searching an index created with 8.3

Re: Lucene 8.7 error searching an index created with 8.3

Re: Lucene 8.7 error searching an index created with 8.3

6 matches

Site Navigation

Mail list logo

Footer information