You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/02 12:47:00 UTC
[jira] [Commented] (SPARK-26924) Fix CRAN hack as soon as Arrow is
available on CRAN
[ https://issues.apache.org/jira/browse/SPARK-26924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831594#comment-16831594 ]
Hyukjin Kwon commented on SPARK-26924:
--------------------------------------
I am going to make this as a standalone issue. I dont' think we can fix it within 3.0.0
> Fix CRAN hack as soon as Arrow is available on CRAN
> ---------------------------------------------------
>
> Key: SPARK-26924
> URL: https://issues.apache.org/jira/browse/SPARK-26924
> Project: Spark
> Issue Type: Sub-task
> Components: SparkR, SQL
> Affects Versions: 3.0.0
> Reporter: Hyukjin Kwon
> Priority: Major
>
> Arrow optimization was added but Arrow is not available on CRAN.
> So, it had to add some hacks to avoid CRAN check in SparkR side. For example, see
> https://github.com/apache/spark/search?q=requireNamespace1&unscoped_q=requireNamespace1
> These should be removed to properly check CRAN in SparkR
> See also ARROW-3204
--
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