Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure cross_fields always uses valid term statistics (#90278) #90314

Merged
merged 2 commits into from Sep 23, 2022

Conversation

jtibshirani
Copy link
Contributor

In #89016 we adjusted the cross_fields scoring formula to prevent negative
scores. This fix accidentally dropped another important fix that was added in
#41938. Specifically, we need to make sure to take the minimum between the
document frequency (actualDf) and the minimum total term frequency
(minTTF). Otherwise, we can produce invalid term statistics where the total
term frequency is less than the document frequency.

Backport of #90278

In elastic#89016 we adjusted the `cross_fields` scoring formula to prevent negative
scores. This fix accidentally dropped another important fix that was added in
elastic#41938. Specifically, we need to make sure to take the minimum between the
document frequency (`actualDf`) and the minimum total term frequency
(`minTTF`). Otherwise, we can produce invalid term statistics where the total
term frequency is less than the document frequency.

Fixes elastic#90275
@jtibshirani jtibshirani added >regression :Search/Ranking Scoring, rescoring, rank evaluation. v8.4.3 labels Sep 23, 2022
@elasticsearchmachine elasticsearchmachine added the Team:Search Meta label for search team label Sep 23, 2022
@elasticsearchmachine
Copy link
Collaborator

Hi @jtibshirani, I've created a changelog YAML for you.

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-search (Team:Search)

@ppf2
Copy link
Member

ppf2 commented Sep 26, 2022

@jtibshirani Thx for the fix! btw, there appears to be some formatting issues with the release notes change. When clicking on 8.4.2 release notes, it shows a blank page. It looks like all the content (including bugs and enhancements) is now listed under the subheading "Known issues".

image

@jtibshirani
Copy link
Contributor Author

Oops, thanks for catching this @ppf2. I just pushed a fix.

jpountz added a commit to jpountz/elasticsearch that referenced this pull request Sep 27, 2022
jpountz added a commit that referenced this pull request Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>regression release highlight :Search/Ranking Scoring, rescoring, rank evaluation. Team:Search Meta label for search team v8.4.3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants