-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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: Improve comments in EnforceDistribution tests #8474
Conversation
@@ -928,7 +928,7 @@ fn add_roundrobin_on_top( | |||
// If any of the following conditions is true | |||
// - Preserving ordering is not helpful in terms of satisfying ordering requirements | |||
// - Usage of order preserving variants is not desirable | |||
// (determined by flag `config.optimizer.bounded_order_preserving_variants`) | |||
// (determined by flag `config.optimizer.prefer_existing_sort`) |
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.
this config option was renamed to prefer_existing_sort but some of the comments and variable names refer to the old name
@@ -2056,23 +2056,33 @@ pub(crate) mod tests { | |||
} | |||
|
|||
/// Runs the repartition optimizer and asserts the plan against the expected | |||
/// Arguments |
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.
I found it very hard to read some of the tests as a line like this
assert_optimized!(expected, physical_plan, false, true);
As I had to go back to the macro definitions several times to remember what the false
and true
parameters meant
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.
Thanks @alamb. This Pr is LGTM!.
Which issue does this PR close?
related to #8451
Rationale for this change
While working on a reproducer for #8451 I noticed several things that could be improved in the EnforceDistribution tests
What changes are included in this PR?
Are these changes tested?
Covered by existing tests
Are there any user-facing changes?
No. It is a code cleanup only