You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Michael Armbrust (JIRA)" <ji...@apache.org> on 2014/10/03 21:37:34 UTC

[jira] [Resolved] (SPARK-1671) Cached tables should follow write-through policy

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

Michael Armbrust resolved SPARK-1671.
-------------------------------------
    Resolution: Fixed

I'm gonna mark this as resolved now that we do at least invalidate the cache when writing through.  We can create a follow up JIRA for partial invalidation if we want.

> Cached tables should follow write-through policy
> ------------------------------------------------
>
>                 Key: SPARK-1671
>                 URL: https://issues.apache.org/jira/browse/SPARK-1671
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 1.0.0
>            Reporter: Cheng Lian
>            Assignee: Michael Armbrust
>              Labels: cache, column
>
> Writing (insert / load) to a cached table causes cache inconsistency, and user have to unpersist and cache the whole table again.
> The write-through policy may be implemented with {{RDD.union}}.



--
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