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 2019/01/25 04:29:00 UTC
[jira] [Assigned] (SPARK-26708) Incorrect result caused by
inconsistency between a SQL cache's cached RDD and its physical plan
[ https://issues.apache.org/jira/browse/SPARK-26708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apache Spark reassigned SPARK-26708:
------------------------------------
Assignee: Apache Spark (was: Maryann Xue)
> Incorrect result caused by inconsistency between a SQL cache's cached RDD and its physical plan
> -----------------------------------------------------------------------------------------------
>
> Key: SPARK-26708
> URL: https://issues.apache.org/jira/browse/SPARK-26708
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.4.0
> Reporter: Xiao Li
> Assignee: Apache Spark
> Priority: Blocker
> Labels: correctness
>
> When performing non-cascading cache invalidation, {{recache}} is called on the other cache entries which are dependent on the cache being invalidated. It leads to the the physical plans of those cache entries being re-compiled. For those cache entries, if the cache RDD has already been persisted, chances are there will be inconsistency between the data and the new plan. It can cause a correctness issue if the new plan's {{outputPartitioning}} or {{outputOrdering}} is different from the that of the actual data, and meanwhile the cache is used by another query that asks for specific {{outputPartitioning}} or {{outputOrdering}} which happens to match the new plan but not the actual data.
--
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