[
https://issues.apache.org/jira/browse/SPARK-16581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431492#comment-15431492
]
Felix Cheung commented on SPARK-16581:
--------------------------------------
Certainly - I don't think we should bite off more than we could chew.
re: API - perhaps we should consider an S4 class as a wrapper/context (and
changes the R->JVM functions to S4) - it would make it easier to
update/evolve/make breaking changes to them.
> Making JVM backend calling functions public
> -------------------------------------------
>
> Key: SPARK-16581
> URL: https://issues.apache.org/jira/browse/SPARK-16581
> Project: Spark
> Issue Type: Sub-task
> Components: SparkR
> Reporter: Shivaram Venkataraman
>
> As described in the design doc in SPARK-15799, to help packages that need to
> call into the JVM, it will be good to expose some of the R -> JVM functions
> we have.
> As a part of this we could also rename, reformat the functions to make them
> more user friendly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
