erate over matches and compute scores.
> >
> > The cost of a scorer is the expected number of matching documents for
> this
> > scorer. It is useful in order to run operations in the optimal order
> >
> > Your observation of the behaviour of your BooleanQuery with SHOULD
> matching sub queries.
>
> Le jeu. 30 nov. 2017 à 16:39, Vadim Gindin <vgin...@detectum.com> a écrit
> :
>
> > Hi
> >
> > 1) What is the principal difference between COST vs SCORE vs WEIGHT
> >
> > 2) Assume we have BooleanQue
. 30 nov. 2017 à 16:39, Vadim Gindin <vgin...@detectum.com> a écrit :
> Hi
>
> 1) What is the principal difference between COST vs SCORE vs WEIGHT
>
> 2) Assume we have BooleanQuery with 5 TermQuery subqueries that are
> included via SHOULD condition. Assume we have 5
Hi
1) What is the principal difference between COST vs SCORE vs WEIGHT
2) Assume we have BooleanQuery with 5 TermQuery subqueries that are
included via SHOULD condition. Assume we have 5 fields and one subquery is
need to search in one field. Some product of MultiFieldQueryParser. In this
case
