[
https://issues.apache.org/jira/browse/CASSANDRA-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939059#comment-14939059
]
Tyler Hobbs commented on CASSANDRA-10429:
-----------------------------------------
Patch for 3.0 (to keep the changes conservative) with pending CI runs:
* [branch|https://github.com/thobbs/cassandra/tree/CASSANDRA-10429]
*
[testall|http://cassci.datastax.com/view/Dev/view/thobbs/job/thobbs-CASSANDRA-10429-testall/]
*
[dtest|http://cassci.datastax.com/view/Dev/view/thobbs/job/thobbs-CASSANDRA-10429-dtest/]
and trunk:
* [branch|https://github.com/thobbs/cassandra/tree/CASSANDRA-10429-trunk]
*
[testall|http://cassci.datastax.com/view/Dev/view/thobbs/job/thobbs-CASSANDRA-10429-trunk-testall/]
*
[dtest|http://cassci.datastax.com/view/Dev/view/thobbs/job/thobbs-CASSANDRA-10429-trunk-dtest/]
The patch adds a system property specifically to disable flushing after local
schema changes. This defaults to flushing, but the unit test config defaults
to not flushing in order to keep unit test run times short.
> 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)
