[ https://issues.apache.org/jira/browse/CASSANDRA-18040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17635267#comment-17635267 ]
Michael Semb Wever commented on CASSANDRA-18040: ------------------------------------------------ ninja-[fixed|https://github.com/apache/cassandra/commit/6be7fed24276713f4f330b27e37afc126dcc264e] CHANGES.txt > Avoid schema mismatch problems on memtable API misconfiguration > --------------------------------------------------------------- > > Key: CASSANDRA-18040 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18040 > Project: Cassandra > Issue Type: Improvement > Components: Cluster/Schema > Reporter: Branimir Lambov > Assignee: Branimir Lambov > Priority: Urgent > Fix For: 4.1-beta2, 4.1, 4.2 > > > The memtable API requires a definition of the memtable configuration to exist > in {{{}cassandra.yaml{}}}. If that is not the case when a schema change is > received from another node, this can cause the node to reject the schema > change and behave incorrectly. > To fix this, a node should only fail to construct a memtable when it is > validating {{CREATE}} or {{ALTER}} statements, but should fall back to > default when it receives invalid configuration selections in the schema. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org