CollapseRepartition physical optimizer#3991
Conversation
|
Unsure if this is what is meant by #41, but I gave it a shot There's probably more to the optimization that could be done, such as dealing with cases like having a Projection sandwiched between two repartition nodes, or cases like this: Where could potentially collapse the two marked RepartitionExec nodes? Unsure if that is correct. Appreciate any feedback on this |
|
There is a general implementation in below PR, please take a look. |
|
@Jefffrey the physical nodes have information on them ( |
Which issue does this PR close?
Closes #41
Rationale for this change
Add repartition elimination as suggested by #41
What changes are included in this PR?
New physical optimizer to eliminate adjacent
RepartitionExecnodesAre there any user-facing changes?