Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14258
I see - So I was thinking that we could merge this into master as well as
its not going to fail any tests or affect any users building SparkR from source
-- I dont think we make any promises about the master branch to users. As long
as the same code works in branch-2.0 then we can just backport this (if we do
want a separate PR for branch-2.0 thats fine, but its just easier to keep all
the code review on one PR)
@felixcheung @mengxr Any other comments on this ?
---
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
