Hello Vadim,
It looks like your query only supports bulkScorer() and not scorer()?
Unfortunately this is illegal: queries must implement scorer(). Today,
conjunctions never use the bulkScorer API.
Le mer. 25 juil. 2018 à 18:47, Vadim Gindin a écrit :
> Hi all!
>
> I have the following
I think you see it correctly. Currently, only tokenizers can really
safely modify offsets, because only they have access to the correction
logic from the charfilter.
Doing it from a tokenfilter just means you will have bugs...
On Wed, Jul 25, 2018 at 8:27 AM, Michael Sokolov wrote:
> I've run
Hi all!
I have the following BooleanQuery (JSON representation as it is defined in
Elasticsearch):
{
"query" : {
"bool" : {
"must" : {
"custom_query" : { // has own bulkScorer() implementation
...
}
},
"filter" : {
...
I've run into some difficulties with offsets in some TokenFilters I've been
writing, and I wonder if anyone can shed any light. Because characters may
be inserted or removed by prior filters (eg ICUFoldingFilter does this with
ellipses), and there is no offset-correcting data structure available
