Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7055#issuecomment-119163829
@litao-buptsse one JIRA = one logical issue, so I'd generally expect PRs
for one JIRA to be quite similar when back-ported. However this has a lot more
change; are you sure you mean for all of this to be in this PR?
In any event, at this point, your change to `master` ended up very simple
and easy to cherry-pick, so you can close this. When it's merged it can be
back-ported easily. That's standard procedure.
---
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]
