Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/19080
so my whole point of view is, co-partition is a really tricky requirement,
and it's really hard to implicitly guarantee it during shuffle planning. We
should have a weaker guarantee(same number of partitions), and let the operator
itself achieve the co-partition requirement by this guarantee and special
distribution requirement(`HashPartitionedDistribution`).
Also in the future we may have operators that have distribution requirement
for multiple children, but they don't need them to be co-partitioned.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
