[
https://issues.apache.org/jira/browse/CASSANDRA-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939151#comment-14939151
]
Aleksey Yeschenko commented on CASSANDRA-10429:
-----------------------------------------------
The patch is good as is, but I would prefer instead to remove the overload of
{{SchemaKeyspace::mergeSchema}} with the boolean doFlush altogether, and put
the {{cassandra.test.flush_local_schema_changes}} flag check into the
single-argument {{SchemaKeyspace::mergeSchema}}. No good reason to expose the
unsafe method version.
> 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)
