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

Jacek Lewandowski edited comment on CASSANDRA-18441 at 4/19/23 11:22 AM:
-------------------------------------------------------------------------

So summarizing things to be done there:
1. sstable format should have hardcoded its string identifier
2. numeric identifier should be removed and we should include a mapping in key 
cache
3. sstable formats should be discovered via service loader
4. format configuration should look differently - let's use the last proposal 
from [~maedhroz] with nesting
5. let configure sstable properties via yaml/system properties


was (Author: jlewandowski):
So summarizing things to be done there:
1. sstable format should have hardcoded its string identifier
2. numeric identifier should be removed and we should include a mapping in row 
cache
3. sstable formats should be discovered via service loader
4. format configuration should look differently - let's use the last proposal 
from [~maedhroz] with nesting
5. let configure sstable properties via yaml/system properties

> 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