Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14705
Yeah so we can do a couple of things. One is we try to cherry-pick this PR
to branch-2.0 and then fix all the merge conflicts that are thrown. I think
that should handle cases where the method doesn't exist in 2.0 etc.
The other option is to create a new PR that is targeted at branch-2.0 (i.e.
the cherry-pick / merge can be done as a part of development) and then we can
review, merge it.
Let me know if you or @junyangq want to try the second option -- If not I
can try the first one and see how many conflicts there are.
---
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
