Github user hvanhovell commented on the issue:

    https://github.com/apache/spark/pull/14452
  
    We reuse all exchanges (including shuffled ones), see this rule: 
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/exchange/Exchange.scala#L69-L94
    
    The optimizer might be doing us a disservice here, by creating two (or 
more) similar but not the same plans from a single source plan, which will 
result in two separately executed plans.


---
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]

Reply via email to