[
https://issues.apache.org/jira/browse/SPARK-15799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326648#comment-15326648
]
Shivaram Venkataraman commented on SPARK-15799:
-----------------------------------------------
[~sunrui] Your proposal sounds promising. The couple of things we should
investigate are
(a) if there are other R packages which similarly download artifacts during
launch. We should compare this approach to executing some logic while
installing the R package (through say a Makefile)
(b) I think we need to see if different versions of the CRAN R package can work
with different Spark versions or not. Having a one-to-one mapping (i.e. each R
package corresponds to one Spark version) might make it harder for users to
work across different Spark clusters or versions.
> Release SparkR on CRAN
> ----------------------
>
> Key: SPARK-15799
> URL: https://issues.apache.org/jira/browse/SPARK-15799
> Project: Spark
> Issue Type: New Feature
> Components: SparkR
> Reporter: Xiangrui Meng
>
> Story: "As an R user, I would like to see SparkR released on CRAN, so I can
> use SparkR easily in an existing R environment and have other packages built
> on top of SparkR."
> I made this JIRA with the following questions in mind:
> * Are there known issues that prevent us releasing SparkR on CRAN?
> * Do we want to package Spark jars in the SparkR release?
> * Are there license issues?
> * How does it fit into Spark's release process?
--
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
