Repository navigation
perf: Drop RowConverter from GroupOrderingPartial - #14566
Conversation
d7e7376 to
a7324c7
Compare
Micro-benchmark results
|
cccc8ea to
0d778f5
Compare
0d778f5 to
ec21860
Compare
|
Thank you, this looks good to me. Let's get the CI fixed. https://github.com/apache/datafusion/blob/main/datafusion/core/tests/fuzz_cases/aggregate_fuzz.rs should have good coverage for edge cases in group by with partial ordering, so I think this change is safe |
ec21860 to
2961710
Compare
|
Thank you for taking the time to review! |
| impl GroupOrderingPartial { | ||
| pub fn try_new( | ||
| input_schema: &Schema, | ||
| _input_schema: &Schema, |
There was a problem hiding this comment.
This way we can avoid API change, though I don't have a strong preference
There was a problem hiding this comment.
maybe we can add a comment or something as a follow on pr
There was a problem hiding this comment.
Additionally, the input_schema argument in order::GroupOrdering::try_new will also be unnecessary
datafusion/datafusion/physical-plan/src/aggregates/order/mod.rs
Lines 43 to 58 in 1626c00
There was a problem hiding this comment.
I've added a TODO comment to the code
Which issue does this PR close?
Rationale for this change
Faster is better?
What changes are included in this PR?
Are these changes tested?
Yes, added a new test.
Are there any user-facing changes?
No.
(The input_schema argument of GroupOrderingPartial::try_new is no longer used and can be removed, this is not included in this PR)