[
https://issues.apache.org/jira/browse/CASSANDRA-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711255#comment-17711255
]
Sam Tunnicliffe commented on CASSANDRA-18441:
---------------------------------------------
We can (and do) validate metadata changes in TCM before they are applied. All
changes are modelled as transformations from one metadata state to the next and
the CMS node coordinating the change applies the transform before committing it
to the change log, or rejecting the change. So it would be possible to ensure
that constraints enforced by DD (or some equivalent) are enforced and/or
prequisites re: the state of the cluster such as all nodes being on a min
version are met.
One caveat is that the scope of what gets managed via TCM is fairly limited in
5.0 (schema, membership/ownership). I can't see we'd have time/capacity to
implement migration of cluster config from DD in anything like that timescale
(or even that that would be a good idea).
> 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]
