Minor: avoid copying order by exprs in planner #11634
Merged
Conversation
This file contains 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
alamb
commented
Jul 24, 2024
| @@ -87,11 +87,9 @@ impl<'a, S: ContextProvider> SqlToRel<'a, S> { | |||
| input_schema.qualified_field(field_index - 1), | |||
| )) | |||
| } | |||
| e => self.sql_expr_to_logical_expr( | |||
| e.clone(), | |||
There was a problem hiding this comment.
Here is the clone that is avoided.
| @@ -37,7 +37,7 @@ impl<'a, S: ContextProvider> SqlToRel<'a, S> { | |||
| /// If false, interpret numeric literals as constant values. | |||
| pub(crate) fn order_by_to_sort_expr( | |||
| &self, | |||
| exprs: &[OrderByExpr], | |||
| exprs: Vec<OrderByExpr>, | |||
There was a problem hiding this comment.
The internal API changes to take the owned Vec rather than a slice
Dandandan
approved these changes
Jul 24, 2024
|
Thanks @Dandandan |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
N/A
Rationale for this change
While working on #11630 I noticed some cloning in SQL planning that could be avoided
What changes are included in this PR?
Stop cloning
oby_exprAre these changes tested?
Existing CI
Are there any user-facing changes?
No, this is internal only