Expose Spilling Progress Interface in DataFusion #19708
Merged
+134
−17
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
execution
Member
Author
|
cc @2010YOUY01 @adriangb iirc, you worked on this part. |
2010YOUY01
approved these changes
Jan 13, 2026
|
|
||
| /// Information about the current disk usage for spilling | ||
| #[derive(Debug, Clone, Copy)] | ||
| pub struct SpillingProgress { |
Contributor
There was a problem hiding this comment.
Perhaps we can call it SpillingMetricsSnapshot, to make its usage more clear.
Member
Author
There was a problem hiding this comment.
I think SpillingProgress matches the api spilling_progress, which shows the real-time spilling progress.
adriangb
approved these changes
Jan 13, 2026
Contributor
adriangb
left a comment
adriangb
left a comment
There was a problem hiding this comment.
Cool to see this being used this way!
What a nice future when datafusion-cli supports some sleek display of query progress, spilling info, memory use, etc.
Member
Author
|
Thank you for the review! |
xudong963
added a commit
to massive-com/arrow-datafusion
that referenced
this pull request
Jan 15, 2026
<!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes apache#123` indicates that this PR will close issue apache#123. --> - Closes apache#19697 <!-- Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed. Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes. --> <!-- There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. --> <!-- We typically require tests for all PRs in order to: 1. Prevent the code from being accidentally broken by subsequent changes 2. Serve as another way to document the expected behavior of the code If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? --> <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> <!-- If there are any breaking changes to public APIs, please add the `api change` label. -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?