Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/4521#issuecomment-74565322
In general you should open all PRs against master, and we will backport
them manually when merging. Please suggest this in the comments (or after the
fact add the "backport needed" tag on JIRA).
If its a specialized fix that due to conflicts can only be made against a
specific release branch, then its okay to make it against that branch. For
Spark SQL at this point master and branch-1.3 are functionally the same.
Regarding branch-1.2, I would not want to backport something that makes a
change this large to a maintenance branch since it could break existing code.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
