Skip to content

Conversation

@jimexist
Copy link
Member

@jimexist jimexist commented Jun 10, 2021

Which issue does this PR close?

Closes #131

Rationale for this change

a small refactor to hash aggregate planning phase, to make the code more readable, streamlined.

this shall be covered by the current unit tests.

What changes are included in this PR?

Are there any user-facing changes?

no

@jimexist jimexist changed the title refactor hash aggregates Refactor hash aggregates's planner building code Jun 10, 2021
@jimexist jimexist force-pushed the refactor-hash-aggregate branch from 69c8241 to e823b16 Compare June 11, 2021 08:03
Copy link
Contributor

@alamb alamb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a nice cleanup 👍

@alamb alamb merged commit 519698a into apache:master Jun 13, 2021
@jimexist jimexist deleted the refactor-hash-aggregate branch June 13, 2021 11:26
unkloud pushed a commit to unkloud/datafusion that referenced this pull request Mar 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implement hash partitioning

4 participants