You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2018/11/12 05:47:00 UTC
[jira] [Assigned] (SPARK-26014) Deprecate R < 3.4 support
[ https://issues.apache.org/jira/browse/SPARK-26014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apache Spark reassigned SPARK-26014:
------------------------------------
Assignee: Apache Spark
> Deprecate R < 3.4 support
> -------------------------
>
> Key: SPARK-26014
> URL: https://issues.apache.org/jira/browse/SPARK-26014
> Project: Spark
> Issue Type: Improvement
> Components: SparkR
> Affects Versions: 3.0.0
> Reporter: Hyukjin Kwon
> Assignee: Apache Spark
> Priority: Major
>
> See http://apache-spark-developers-list.1001551.n3.nabble.com/discuss-SparkR-CRAN-feasibility-check-server-problem-td25605.html
> R version. 3.1.x is too old. It's released 4.5 years ago.
> R 3.4.0 is released 1.5 years ago. Considering the timing for Spark 3.0, deprecating lower versions, bumping up R to 3.4 might be reasonable option.
> It should be good to deprecate and drop < R 3.4 support.
> If we think about the practice, nothing particular is required within R codes as far as I can tell.
> We will just upgrade Jenkins's R version to 3.4, which mean we're not going to test 3.1 R version (but instead we will test 3.4).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org