[
https://issues.apache.org/jira/browse/SPARK-8684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614990#comment-14614990
]
Vincent Warmerdam commented on SPARK-8684:
------------------------------------------
just tried it all, and it just seems to work on my current branch of
`rstudio-install`.
http://i.imgur.com/QkKq4Sj.png
no clue why we had an 3.1 error before. it might be because of how some parts
are automated now and that we don't run the sparkR.sh command first. can't say
exactly what may have caused it in the past though.
the only annoying thing at the moment seems that if you want to use Rmarkdown,
it will start another sparkR instance because it starts a seperate R-shell to
run code in it. this is solved by stopping spark first before generating the
rmarkdown html file. besides that it seems like a very nice automated install
that will help the R community to get started.
http://i.imgur.com/Ah88K9T.png
> Update R version in Spark EC2 AMI
> ---------------------------------
>
> Key: SPARK-8684
> URL: https://issues.apache.org/jira/browse/SPARK-8684
> Project: Spark
> Issue Type: Improvement
> Components: EC2, SparkR
> Reporter: Shivaram Venkataraman
> Priority: Minor
>
> Right now the R version in the AMI is 3.1 -- However a number of R libraries
> need R version 3.2 and it will be good to update the R version on the AMI
> while launching a EC2 cluster.
--
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
