Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/1327#issuecomment-48504833
As @aarondav mentions, this class has never been 're-used'.
As part of our shuffle consolidation fixes, we actually depend on this
behavior (and enforce it via a closed flag).
I did not want this PR to change the expectation within spark !
Hopefully that PR is going to be submitted later this week or early next
week (currently pending testcases)
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
