[AUDIT][SPARK-40086] Changes to physical plan class hierarchy to reduce redundant shuffles and sorts #7727
Labels
audit_3.4.0
Audit related tasks for 3.4.0
feature request
New feature or request
performance
A performance related task/issue
Is your feature request related to a problem? Please describe.
In apache/spark@b122436564 a number of physical operators have changes to the traits they implement (aggregates, projections, limits, TakeOrderedAndProjectExec).
They now extend
OrderPreservingUnaryExecNode
andPartitioningPreservingUnaryExecNode
and this can avoid redundant shuffles and sorts.Describe the solution you'd like
We likely need to make similar changes if we want to get the same performance improvements.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: