cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10429) Flush schema tables after local schema change
Date Thu, 01 Oct 2015 19:28:27 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940273#comment-14940273
] 

Tyler Hobbs commented on CASSANDRA-10429:
-----------------------------------------

The tests don't appear to introduce any regressions, so committed as {{5c2912d1ce95aacdacb59ccc840b12cd9aa0c8f8}}
to 3.0 and merged to trunk.  Thanks!

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

Mime
View raw message