[
https://issues.apache.org/jira/browse/CASSANDRA-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716850#comment-17716850
]
David Capwell commented on CASSANDRA-18441:
-------------------------------------------
bq. I wonder if we shouldn't leave the version out to be dealt with in a
downgradeability ticket
I am cool with the version being left to a different ticket, as long as this
API allows it (the version being in option allows it)
bq. b.) consistent w/ the big nesting overhaul proposal from CASSANDRA-17292.
Nested configs became more complex than expected, so using a design where
multiple partied were ok with is best IMO, so I prefer sstable.format.[default,
options]. I am ok with the keys under sstable.format to change as defined by
this patch (selected_format, selected, default, etc.). So +1 to the yaml
defined by [~maedhroz]
> Improvements to SSTable format configuration
> --------------------------------------------
>
> Key: CASSANDRA-18441
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18441
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/SSTable
> Reporter: Branimir Lambov
> Assignee: Jacek Lewandowski
> Priority: Normal
> Fix For: 5.x
>
>
> CEP-17 and CASSANDRA-17056 abstracted some interfaces for SSTable format
> implementations and defined a method of plugging in specific configurations.
> This method is brittle and asks users to specify format identifiers whose
> configuration does not provide value but can be the source of conflicts and
> problems. On the other hand it makes important choices non-obvious, as the
> selection of format to write is given by the order of configured interfaces.
> An improved specification mechanism needs to be put in place before Cassandra
> 5 is released.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
