[LUCENE-10039] With a single field, CombinedFieldQuery can score incorrectly

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 8.10
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Julie Tibshirani
• Created: 28/Jul/21 08:57
• Updated: 28/Aug/22 16:24
• Resolved: 28/Jul/21 14:41

Description

When there's only one field, CombinedFieldQuery will ignore its weight while scoring. This makes the scoring inconsistent, since the field weight is supposed to multiply its term frequency.

This can also come up when searching over multiple fields, when some segment happens to contain only one field. The problem was caught by this test:

ant test  -Dtestcase=TestCombinedFieldQuery -Dtests.method=testCopyFieldWithMissingFields -Dtests.seed=8FA982798BC8FEF6 -Dtests.nightly=true

Issue Links

• links to: GitHub Pull Request #229
• links to: GitHub Pull Request #2535