Details
-
Improvement
-
Status: Resolved
-
Urgent
-
Resolution: Fixed
-
4.1-rc1, 4.1, 5.0-alpha1, 5.0
-
None
-
Operability
-
Low Hanging Fruit
-
All
-
None
-
Description
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.
Attachments
Issue Links
- is caused by
-
CASSANDRA-17034 CEP-11: Memtable API implementation
- Resolved