[jira] [Updated] (CASSANDRA-18040) Avoid schema mismatch problems on memtable API misconfiguration

["Branimir Lambov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-18040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Branimir Lambov updated CASSANDRA-18040:
----------------------------------------
    Change Category: Operability
         Complexity: Low Hanging Fruit
           Priority: Urgent  (was: Normal)
             Status: Open  (was: Triage Needed)

> 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
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org