Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/14775
I think the downside of naming them as-is and keeping the signature (`...`
at the end) are that it would be very hard to change or add to the signature
later on (say, to add a context/context_id)
How about naming them `sparkR.callJMethod` or similar for the exported
versions to wrap around the internal ones?
this way we don't have to break internal stuff and could just add a new
method if/when we want.
we could also additional parameter checks or translation as needed that
might not apply to internal stuff, which could also mitigate risk
---
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]
