-
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
Extract drive-by fixes from PR 12135 for easier reviewing #12240
Conversation
It looks like clippy failed due to some internal CI connectivity issue - I don't think I can rerun them by myself. |
Thanks @itsjunetime I have restarted the CI (you do need to be a datafusion committer to restart the jobs individually) One trick to get github to rerun the CI is to close the PR and then reopen it (that will trigger rerunning the whole PR) |
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.
Looks like a very nice set of cleanups to me @itsjunetime -- thank you
@@ -51,12 +51,12 @@ use object_store::{ObjectMeta, ObjectStore}; | |||
/// - the table provider can filter the table partition values with this expression | |||
/// - the expression can be marked as `TableProviderFilterPushDown::Exact` once this filtering | |||
/// was performed | |||
pub fn expr_applicable_for_cols(col_names: &[String], expr: &Expr) -> bool { | |||
pub fn expr_applicable_for_cols(col_names: &[&str], expr: &Expr) -> bool { |
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 is a nice removal of some clones 👍
let rr = as_boolean_array($RIGHT).expect("boolean_op failed to downcast array"); | ||
Ok(Arc::new($OP(&ll, &rr)?)) | ||
}}; | ||
#[inline] |
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.
👍
Which issue does this PR close?
Helps with reviewing of #12135
Rationale for this change
These are just a few changes that make the code cleaner/easier to understand/etc that I added when filing #12135. It was pointed out to me, though, that these make the PR harder to review as there's a lot of changes not directly related to the PR. So I'm pulling those changes into this PR so that they are hidden from the diff once this is merged, thus making the PR easier to review.
What changes are included in this PR?
A few clean-ups that shouldn't change behavior at all.
Are these changes tested?
All tests pass just like they do on main.
Are there any user-facing changes?
Shouldn't be