[jira] [Resolved] (SPARK-4713) SchemaRDD.unpersist() should not raise exception if it is not cached.

["Michael Armbrust (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Armbrust resolved SPARK-4713.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0

Issue resolved by pull request 3572
[https://github.com/apache/spark/pull/3572]

> SchemaRDD.unpersist() should not raise exception if it is not cached.
> ---------------------------------------------------------------------
>
>                 Key: SPARK-4713
>                 URL: https://issues.apache.org/jira/browse/SPARK-4713
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Cheng Hao
>            Priority: Minor
>             Fix For: 1.3.0
>
>
> Unpersist a uncached RDD, will not raise exception, for example:
> {panel}
> val data = Array(1, 2, 3, 4, 5)
> val distData = sc.parallelize(data)
> distData.unpersist(true)
> {panel}
> But the SchemaRDD will throws exception if the SchemaRDD is not cached. Since SchemaRDD is the subclasses of the RDD, we should follow the same behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org