[
https://issues.apache.org/jira/browse/CASSANDRA-19841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-19841:
--------------------------------------
Resolution: Won't Fix
Status: Resolved (was: Open)
spoke with [~blambov] in slack and going to close this ticket as won't do. The
reason is that adding defaults would take the control away from operators.
Lets say we add "trie" as a new default but operators don't wish to support it,
users would be able to use in their DDL and take out all control from
operators...
> Memtable configs don't have defaults for each format supported
> --------------------------------------------------------------
>
> Key: CASSANDRA-19841
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19841
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
> Reporter: David Capwell
> Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> We added support to change memtable and sstables via yaml but it seems we
> only added defaults for sstables and missed them for memtables. We document
> recommended defaults in config/cassandra.yaml but that isn’t present in
> Config nor is it present in the resolution logic that translates the config
> to our maps, this means that anyone who defines their own yaml won’t have
> “skiplist”, “trie”, or “shardedskiplist” as default options to pick from and
> must know how to define them.
> To make it easier for users we should provide defaults that could be
> overridden by users, just like we did for SSTables
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
