-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Refactor Expr::GetIndexedField to use a struct
#3860
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
Conversation
| } | ||
| } | ||
|
|
||
| #[derive(Clone, PartialEq, Eq, Hash)] |
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.
Overlooked it because I wasn't sure what expression GetIndexedField corresponds to, but should add a comment here explaining the purpose of this struct
Expr::GetIndexedField to use a struct
andygrove
left a comment
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.
LGTM. Thanks @charlesbluca
| } | ||
|
|
||
| #[derive(Clone, PartialEq, Eq, Hash)] | ||
| pub struct GetIndexedField { |
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 think we can just re-use the docs from the Expr::GetIndexField enum variant here:
| pub struct GetIndexedField { | |
| /// Returns the field of a [`arrow::array::ListArray`] or [`arrow::array::StructArray`] by key | |
| pub struct GetIndexedField { |
|
There is another PR open for the same work - #3838 |
|
Ah my bad completely missed that, happy to close in that case |
Which issue does this PR close?
Related to #2175 and #3807.
Rationale for this change
Continuing the work outlined in #3807 to bring
Exprvariants more in line withLogicalPlanvariants.What changes are included in this PR?
Refactors
Expr::GetIndexedFieldto use a struct.Are there any user-facing changes?
No