You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Shivaram Venkataraman (JIRA)" <ji...@apache.org> on 2016/08/18 16:59:21 UTC
[jira] [Issue Comment Deleted] (SPARK-16581) Making JVM backend
calling functions public
[ https://issues.apache.org/jira/browse/SPARK-16581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shivaram Venkataraman updated SPARK-16581:
------------------------------------------
Comment: was deleted
(was: I am not sure the issues are very related though
1. The JVM->R access methods are mostly to call into any Java method (like say in SystemML). I think we have reasonable clarity on what to make public here which is callJMethod and callJStatic. There is also some discussion on supporting custom GC using cleanup.jobj in the SPARK-16611
2. The RDD / RBackend are not directly related to this I think. The RDD ones are about our UDFs not having some features right now and we can continue discussing that in SPARK-16611 or other JIRAs ?)
> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org