Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/7572#issuecomment-123462071
I think the lack of a JIRA earlier is largely a matter of users not even
being able to sort out the confusing behavior sufficiently to be able to file a
useful bug report. After Imran's heroic effort to unwind what was going on, it
is pretty clear that the prior behavior was badly broken. I know from
experience that the old behavior causes significant issues in production
environments, and I know that I will be using this fix in a 1.4 context even if
it is not merged into the 1.4 distribution -- but I'd rather not have to
maintain divergent code.
Certainly if this were a regression we'd be looking more at "must fix", but
a significant problem that can be resolved without violating our versioning
guarantees falls pretty clearly into "should fix", imo.
@pwendell
---
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]
