[
https://issues.apache.org/jira/browse/CASSANDRA-18040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Branimir Lambov updated CASSANDRA-18040:
----------------------------------------
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed as
[9f58d76f3841864be11f5b9c4534027451328569|https://github.com/apache/cassandra/commit/9f58d76f3841864be11f5b9c4534027451328569]
(4.1) and
[e08c7a6295eed716e9973fbd809dfca32d68a3e8|https://github.com/apache/cassandra/commit/e08c7a6295eed716e9973fbd809dfca32d68a3e8]
(trunk).
> 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-rc, 4.x
>
>
> 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
