minor: refactor with assert_or_internal_err!() in datafusion/physical-optimizer
#18732
+43
−41
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
kumarUjjawal
commented
Nov 15, 2025
| if coalesce_fetch < sort_fetch { | ||
| return internal_err!( | ||
| "CoalescePartitionsExec fetch [{:?}] should be greater than or equal to SortExec fetch [{:?}]", coalesce_fetch, sort_fetch | ||
| fetch = match fetch { |
Contributor
Author
There was a problem hiding this comment.
I was a little unsure about this block, would like a feedback.
kumarUjjawal
changed the title
assert_or_internal_err!() in datafusion/physical-optimizerassert_or_internal_err!() in datafusion/physical-optimizer
14 tasks
2010YOUY01
approved these changes
Nov 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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?
assert_or_internal_err!()across the codebase #18613Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?