[ 
https://issues.apache.org/jira/browse/CASSANDRA-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714204#comment-17714204
 ] 

Caleb Rackliffe commented on CASSANDRA-18441:
---------------------------------------------

Looks like a reasonable plan to me.

As far as the YAML format goes, I guess the only thing my proposal might not 
handle cleanly is third-party formats. I'm not really sure how important that 
is though, to be honest. If someone invents a new format, they can either add 
its name/config into the YAML in a fork or wherever they run it, or contribute 
it to the project. Even if they don't do that, as long as their custom format 
hooks up to the {{ServiceLoader}} framework, they should be able to define it 
as the primary format strictly via the system property w/o any YAML changes in 
the first place.

(In either case, anything defined in either system properties or YAML around 
this is just an overlay after {{ServiceLoader}} finds all the available 
formats. ex. You need to know the available formats before you validate the 
choice of primary/default.)

> 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]

Reply via email to