-
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
Remove OwnedTableReference
and OwnedSchemaReference
#9933
Conversation
I have run benches, there is slight noise for most of benches, however there are sometimes regression 4%, sometimes performance improvement 4%. My feeling once we unify |
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 like this change 👍. What is the process to mark this as a breaking change users should be aware of when updating?
We add a |
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 looks really nice -- thank you @comphead 🙏
.collect::<Vec<_>>(); | ||
left_fields.into_iter().chain(right_fields).collect() | ||
} | ||
JoinType::Left => { | ||
// left then right, right set to nullable in case of not matched scenario | ||
let left_fields = left_fields | ||
.map(|(q, f)| (q.map(|r| r.to_owned_reference()), f.clone())) | ||
.map(|(q, f)| (q.cloned(), f.clone())) |
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.
👍
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'm thinking to try removing all this clones in future... if possible
I'll wait for couple of more hours, if there is no more comments, I'll merge to avoid conflicts on upcoming analyzer changes |
Which issue does this PR close?
Related to #9764
Followup on #9824
Rationale for this change
In #9824 we switched to use
Arc
smart pointers instead ofCoW<&'a>
. Having done that the auxiliary types supporting lifetimes became obsolete.What changes are included in this PR?
The PR removes
OwnedTableReference
andOwnedSchemaReference
types which are now obsolete.Are these changes tested?
Are there any user-facing changes?