Jim Ferenczi c22a2cea12 BlendedTermQuery should ignore fields that don't exists in the index (#41125) ...

Today the blended term query detects if a term exists in a field by looking at the term statistics in the index.
However the value to indicate that a term has no occurence in a field have changed in Lucene. A non-existing term now returns
a doc and total term frequency of 0. Because of this disrepancy the blended term query picks 0 as the minimum frequency for a term
even if other fields have documents for this terms. This confuses the term queries that the blending creates since some of them
contain a custom state that indicates a frequency of 0 even though the term has some occurence in the field. For these terms an exception
is thrown because the term query always checks that the term state's frequency is greater than 0 if there are documents associate to it.
This change fixes this bug by ignoring terms with a doc freq of 0 when the blended term query picks the minimum term frequency among the
requested fields.

Closes #41118

2019-04-16 16:25:42 +02:00

..

licenses

Upgrade to Lucene release 8.0.0 (#39998)

2019-03-13 18:11:50 +01:00

src

BlendedTermQuery should ignore fields that don't exists in the index (#41125)

2019-04-16 16:25:42 +02:00

build.gradle

[Backport] Replace usages RandomizedTestingTask with built-in Gradle Test (#40978) (#40993)

2019-04-09 11:52:50 -07:00