Don't index ranges including NOW in percolator #52748
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, date ranges queries using
NOW
-based date math are rewritten toMatchAllDocs
queries when being preprocessed for the percolator. However,since we added the verification step, this can result in incorrect matches when
percolator queries are run without scores. This commit changes things to instead
wrap date queries that use
NOW
with a newDateRangeIncludingNowQuery
.This is a simple wrapper query that returns its delegate at rewrite time, but it can
be detected by the percolator
QueryAnalyzer
and be dealt with accordingly.This also allows us to remove a method on
QueryRewriteContext
, and push alllogic relating to
NOW
-based ranges into theDateFieldMapper
.Fixes #52617