Block-max WAND and other optimizations that improve the retrieval of
top hits (block-max WAND is about disjunctions, but we have
optimizations for conjunctions, phrases and boolean queries that mix
MUST and SHOULD clauses too) are only applied when the score mode is
TOP_SCORES indeed.
The level in
@Adrien Grand mailto:jpou...@gmail.com>>. Thanks for your
reply.
The explanation ` skip low-scoring matches` is great, I looked up some docs
and inspect some related code.
I noticed the ` block-max WAND` mode only work when ScoreMode.TOP_SCORES is
used, is right? (The basic TermQuery wo
I'm not au courant with highlighters as I used to be. I think some of them
work using postings, and for those, no, you wouldn't be able to highlight
stop words. But maybe you can use the old default highlighter that would
reanalyze the document from a stored field, using an Analyzer that doesn't
re
To clarify, the scoring process is not accelerated because we
terminate early but because we can skip low-scoring matches (there
might be competitive hits at the very end of the index).
CompetitiveImpactAccumulator is indeed related to WAND. It helps store
the maximum score impacts per block of do
Hi,
We discuss some topic from https://github.com/apache/lucene-solr/pull/595. As
Atri Sharma propose discuss with the java dev list.
Impact `frequency ` and `norm ` just to accelerate the `score process` which
`terminate early`.
In impact mode, `CompetitiveImpactAccumulator` will record