[
https://issues.apache.org/jira/browse/SPARK-15799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318769#comment-15318769
]
Shivaram Venkataraman commented on SPARK-15799:
-----------------------------------------------
I dont think there are any license issues and at least before we merged SparkR
into the apache the package passed all the CRAN checks. The only problem is
that we might need to ship the entire Spark assembly JAR (or all the jars that
we have with the new release structure) to make the package work without
additional downloads. Some other minor things that might make it challenging to
use SparkR directly from CRAN
1. Matching versions between client and cluster versions of Spark. This is
still a requirement today but the main difference is that people might upgrade
CRAN packages separately from their Spark clusters say.
2. Figuring out where to put scripts like spark-submit that can be used to
submit batch jobs. This isn't something normal R packages offer so I'm not sure
there are existing practices we can follow here.
> 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
