You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2015/09/16 21:32:45 UTC
[jira] [Commented] (CASSANDRA-10359) Saved caches use ambigous
keyspace and CF name to identify tables
[ https://issues.apache.org/jira/browse/CASSANDRA-10359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790999#comment-14790999 ]
Robert Stupp commented on CASSANDRA-10359:
------------------------------------------
There's a possible data race condition as described in [this comment|https://issues.apache.org/jira/browse/CASSANDRA-10155?focusedCommentId=14790981&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14790981]
> Saved caches use ambigous keyspace and CF name to identify tables
> -----------------------------------------------------------------
>
> Key: CASSANDRA-10359
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10359
> Project: Cassandra
> Issue Type: Bug
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
> Fix For: 3.x, 2.1.x, 2.2.x
>
>
> 2i don't have a unique handle. Robert suggested writing the schema digests into the file and checking that they match before loading caches.
> Schema changes would temporarily invalidate saved caches, but the next time they are saved they would be usable again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)