spark-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From viirya <>
Subject [GitHub] spark issue #18694: [SPARK-21492][SQL] Memory leak in SortMergeJoin
Date Fri, 21 Jul 2017 05:31:49 GMT
Github user viirya commented on the issue:
    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 or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message