-
Notifications
You must be signed in to change notification settings - Fork 1.8k
minor: refactor with assert_or_internal_err!() in datafusion/physical-plan
#18730
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
minor: refactor with assert_or_internal_err!() in datafusion/physical-plan
#18730
Conversation
assert_or_internal_err!() in datafusion/physical-planassert_or_internal_err!() in datafusion/physical-plan
| if self.mode == PartitionMode::Partitioned && left_partitions != right_partitions | ||
| { | ||
| return internal_err!( | ||
| if self.mode == PartitionMode::Partitioned { | ||
| assert_eq_or_internal_err!( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're gonna do this refactor we should refactor this entire if statement away, instead of only moving half the condition inside it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
datafusion/physical-plan/src/test.rs
Outdated
| "Column {:?} is not found in the original schema of the TestMemoryExec", | ||
| ambiguous_column | ||
| .as_ref() | ||
| .expect("checked by assert_or_internal_err!") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just unwrap it, expect here adds unnecessary noise
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
…cal-plan` (apache#18730) ## 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. --> - Part of apache#18613 ## Rationale for this change <!-- 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. --> ## What changes are included in this PR? <!-- 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. --> ## Are these changes tested? <!-- 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)? --> ## Are there any user-facing changes? <!-- 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. -->
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?