Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/19257
Maybe we need to rethink about the planning phase for adding shuffles. How
about we add a placeholder for shuffle node and then replace the placeholder
with actual shuffle node in `EnsureRequirements`? Then we can make sure the
plan tree is always resolved.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
