EnableScoring::Disabled - optional Searcher #1780
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.
We have a custom
Query
that requires theSearcher
inweight(..)
(for looking up cached data used in matching that is kept warmed and keyed on searcher generation), even when scoring is disabled (e.g. usingDocSetCollector
)So I am proposing to make a further API change on top of #1667 such that
EnableScoring::Disabled
can contain an optionalSearcher
, and nudging towards providing it when available.Searcher::search(..)
has been updated accordingly.