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

Cleanup Repartition Exec code #538

Merged
merged 3 commits into from
Jun 13, 2021
Merged

Conversation

alamb
Copy link
Contributor

@alamb alamb commented Jun 10, 2021

Rationale for this change

The body of RepartitionExec::execute is long and highly indented, and has a bunch of metrics related code that obscures how it works, in my opinion.

What changes are included in this PR?

As suggested by @tustvold in #521 (comment), attempt to make the code clearer and error conditions easier to reason about by:

Changes:

  1. Factor the body of the repartition into its own async function
  2. Grouped the metrics into a RepartitionMetrics struct for convenience
  3. Refactored repeated code into SQLMetric::add_elapsed and reduced duplication

I still think the metrics could still be made better, and I hope to work on that at a later date.

Are there any user-facing changes?

No

channels.insert(partition, (sender, receiver));
}
// Use fixed random state
let random = ahash::RandomState::with_seeds(0, 0, 0, 0);

// launch one async task per *input* partition
for i in 0..num_input_partitions {
let random_state = random.clone();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

All of this code was moved to pull_from_input

@alamb alamb added the datafusion Changes in the datafusion crate label Jun 10, 2021
@alamb alamb merged commit d382854 into apache:master Jun 13, 2021
@alamb alamb deleted the alamb/repartion_clean branch October 6, 2022 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
datafusion Changes in the datafusion crate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants