Skip to content

Fix needsScore computation in GlobalOrdCardinalityAggregator #113129

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

Merged
merged 6 commits into from
Oct 1, 2024

Conversation

iverase
Copy link
Contributor

@iverase iverase commented Sep 18, 2024

When adding dynamic pruning for GlobalOrdCardinalityAggregator, it was introduced a bug on how we compute needsScore as it does not take into account if the cardinality has parent, so in that cases it might return the wrong answer. This commit fixes that.

fixes #112975

@elasticsearchmachine elasticsearchmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Sep 18, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-analytical-engine (Team:Analytics)

@elasticsearchmachine
Copy link
Collaborator

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

@iverase iverase merged commit ab520d9 into elastic:main Oct 1, 2024
16 checks passed
@iverase iverase deleted the bugScoring branch October 1, 2024 07:01
iverase added a commit to iverase/elasticsearch that referenced this pull request Oct 1, 2024
…#113129)

Only use TOP_DOCS if we are going to use dynamic pruning.
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
8.x
8.15

iverase added a commit to iverase/elasticsearch that referenced this pull request Oct 1, 2024
…#113129)

Only use TOP_DOCS if we are going to use dynamic pruning.
elasticsearchmachine pushed a commit that referenced this pull request Oct 1, 2024
#113833)

Only use TOP_DOCS if we are going to use dynamic pruning.
elasticsearchmachine pushed a commit that referenced this pull request Oct 1, 2024
#113832)

Only use TOP_DOCS if we are going to use dynamic pruning.
matthewabbott pushed a commit to matthewabbott/elasticsearch that referenced this pull request Oct 4, 2024
…#113129)

Only use TOP_DOCS if we are going to use dynamic pruning.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/Aggregations Aggregations >bug Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v8.15.3 v8.16.0 v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Nested terms and cardinality aggregation causes scoring exception
3 participants