-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Reorganize the GroupColumn implementations into more coherent modules #13262
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Once #12996 is merged, this would be a good first issue I think as it is just code movement and somewhat mechanical It would be a good way to get introduced to the code |
take |
#12996 has now merged so this issue should now be unblocked |
@Chen-Yuan-Lai Have you started on this? |
Yes, I'm working on this, but have some questions:
|
Or you can name it as multi_column.rs and add the submodule in this this file. Structure is similar to I think it is fine to place test in separated file. |
Is your feature request related to a problem or challenge?
While reviewing #12996 I noticed that all the implementations of
GroupColumn
for different types were indatafusion/physical-plan/src/aggregates/group_values/group_column.rs
which is:GroupValuesColumn
: https://github.com/apache/datafusion/blob/main/datafusion/physical-plan/src/aggregates/group_values/column.rs#L94-L93Describe the solution you'd like
I would like to propose rearrainging the code:
primitive.rs
,bytes.rs
, etc)Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: