[
https://issues.apache.org/jira/browse/CASSANDRA-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714102#comment-17714102
]
Branimir Lambov commented on CASSANDRA-18441:
---------------------------------------------
I don't understand why we would want to define more than one write
configuration if we only identify the configuration by format name.
Either we specify the write format per table, or we use the same write
configuration for everything. If we do the former, to me the most important
thing is to allow multiple configurations for the same format. For example, one
with {{row_index_granularity: 0.5kib}} and one with the default
{{row_index_granularity: 16kib}}. Eventually existing schema properties like
bloom filter chance or compression would move into the format configuration.
To keep changes limited, I would prefer to not implement any per-table
configuration at this point, and thus only expose and configure the single
write format to use.
> 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]
