Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18694
This only makes sense if the downstream operators consume the iterator of
SortMergeJoin first and then performs its work. If the downstream operators are
piped with SortMergeJoin, once the iterator from SortMergeJoin is exhausted,
even one side in the Join is not exhausted, the whole pipe is finished and the
cleanup will be run, right?
Compared with the overhead this change brings in, how much it improves the
performance?
---
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]
