mingmwang commented on PR #6009: URL: https://github.com/apache/arrow-datafusion/pull/6009#issuecomment-1508296731
> Good points. I esp. like the "keep ordering VS keep partition" semantics. How about we split `UnionExec` into two node types then? I think this would avoid a lot of confusion. At the very begin, I thought we could have two types of Union, a normal `UnionExec` and `PartitionAwareUnionExec`. We could have a physical rule to replace `UnionExec` to `PartitionAwareUnionExec` if capable, and a configure option to turn on/off the rule. But because the partition and ordering info are not static, they are changed dynamically. I not sure how this rule will interact with the enforcer rules. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
