Skip to content

Enable aggregation spill only when all aggregations are spillable#11353

Merged
sopel39 merged 1 commit intotrinodb:masterfrom
starburstdata:ks/enable_agg
Mar 8, 2022
Merged

Enable aggregation spill only when all aggregations are spillable#11353
sopel39 merged 1 commit intotrinodb:masterfrom
starburstdata:ks/enable_agg

Conversation

@sopel39
Copy link
Copy Markdown
Member

@sopel39 sopel39 commented Mar 7, 2022

Description

Is this change a fix, improvement, new feature, refactoring, or other?

bugfix

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

core query engine

How would you describe this change to a non-technical end user or system administrator?

queries might return wrong results when spill was enabled and aggregation was used

Related issues, pull requests, and links

Documentation

(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

( ) No release notes entries required.
( ) Release notes entries required with the following suggested text:

# General
* Fix aggregation results when distinct or ordered aggregation is used with spilling. ({issue}`issuenumber`)

@sopel39 sopel39 requested a review from dain March 7, 2022 16:21
@cla-bot cla-bot bot added the cla-signed label Mar 7, 2022
@sopel39 sopel39 merged commit eb37785 into trinodb:master Mar 8, 2022
@sopel39 sopel39 deleted the ks/enable_agg branch March 8, 2022 09:50
@sopel39 sopel39 mentioned this pull request Mar 8, 2022
@github-actions github-actions bot added this to the 373 milestone Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants