You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2015/10/01 01:30:04 UTC

[jira] [Created] (CASSANDRA-10429) Flush schema tables after local schema change

Tyler Hobbs created CASSANDRA-10429:
---------------------------------------

             Summary: Flush schema tables after local schema change
                 Key: CASSANDRA-10429
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10429
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
            Reporter: Tyler Hobbs
            Assignee: Tyler Hobbs
            Priority: Minor
             Fix For: 3.0.0 rc2


In CASSANDRA-7327, we disabled the normal flush of system schema tables after "local" schema changes to improve the runtime of unit tests.  However, there are some cases where this flush is necessary for schema durability.  For example, if a custom secondary index needs to make schema changes as part of it's creation, this is desirable.



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