[
https://issues.apache.org/jira/browse/CASSANDRA-18040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633872#comment-17633872
]
Branimir Lambov commented on CASSANDRA-18040:
---------------------------------------------
Tests:
[4.1|https://app.circleci.com/pipelines/github/blambov/cassandra/279/workflows/4b378d6d-c72f-49f2-ba32-e1ddfd98bcef]
[trunk|https://app.circleci.com/pipelines/github/blambov/cassandra/280/workflows/8e4033ca-5d57-47cb-841b-23ecb3f92fe5]
> 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
