Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/12258
Also, @vanzin, a process note here: my understanding is that 2.0 should
only have blockers / regressions merged at this point. Based on the JIRA, it
looks like this bug has existed for along time so is not a regression, and
doesn't cause a failure or hang -- just unnecessary additional work to re-run
the task. So, it should not have been merged into the 2.0 release. As a
result (and also because of the concerns I addressed above, which make me
concerned that this may introduce additional issues into 2.0) I'd advocate for
reverting this in 2.0. @rxin thoughts, since you're the release manager?
---
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]
