Repository navigation
docs: mention output_rows_skew on partitioned operators in explain-usage - #26048
Merged
gabotechs merged 1 commit intoOct 5, 2026
Merged
Conversation
github-actions
Bot
added
the
documentation
gabotechs
approved these changes
Oct 5, 2026
gabotechs
enabled auto-merge
October 5, 2026 09:38
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #26048 +/- ##
=======================================
Coverage 82.66% 82.66%
=======================================
Files 1147 1147
Lines 446357 446430 +73
Branches 446357 446430 +73
=======================================
+ Hits 368971 369032 +61
+ Misses 54997 54996 -1
- Partials 22389 22402 +13 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Contributor
|
Thanks @LiaCastaneda for quickly completing this followup! |
Omega359
pushed a commit
to Omega359/arrow-datafusion
that referenced
this pull request
Oct 11, 2026
…age (apache#26048) Follow-up to apache#25977. ## Which issue does this PR close? <!-- 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 #. ## Rationale for this change now output_rows_skew is used in other operators than DataSourceExec, but I forgot to add it to the doc ## What changes are included in this PR? Small comment in the doc mentioning output_rows_skew is also used for other operators than DataSourceExec(parquet) ## What is the testing strategy for 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 Briefly describe how this PR is tested, and point to the specific tests you added. For example: 'This new feature is covered by the `sqllogictest` cases added in `foo.slt`'. If this PR does not add tests, explain why. For example, if the change is already covered by existing tests, please mention it. You should also check the `codecov` bot reply on this PR to confirm the changed code is exercised. --> ## Are there any user-facing changes? Just doc.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Follow-up to #25977.
Which issue does this PR close?
Rationale for this change
now output_rows_skew is used in other operators than DataSourceExec, but I forgot to add it to the doc
What changes are included in this PR?
Small comment in the doc mentioning output_rows_skew is also used for other operators than DataSourceExec(parquet)
What is the testing strategy for this PR?
Are there any user-facing changes?
Just doc.