You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2013/08/20 16:03:51 UTC
[jira] [Commented] (CASSANDRA-5904) Don't announce schema version
until we've loaded the changes locally
[ https://issues.apache.org/jira/browse/CASSANDRA-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744979#comment-13744979 ]
Aleksey Yeschenko commented on CASSANDRA-5904:
----------------------------------------------
+1
> Don't announce schema version until we've loaded the changes locally
> --------------------------------------------------------------------
>
> Key: CASSANDRA-5904
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5904
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 1.2.9
>
> Attachments: 5904.txt
>
>
> Currently, we call updateSchemaAndAnnounce (which sets the schema version in the system table and announce it on gossip) in DefsTable.mergeSchema as soon as we've persisted the schema mutation but *before* we've actually loaded new/updated KS/CF locally. This makes it impossible to reliably check for schema agreement in a cluster as even if all nodes have the same version set in the system tables, you could still get an insert on a new table rejected because the table hasn't been loaded yet.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira