You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (Jira)" <ji...@apache.org> on 2026/07/02 13:07:00 UTC

[jira] [Comment Edited] (CASSANDRA-20736) Add CMS membership as a field in ClusterMetadata

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

Sam Tunnicliffe edited comment on CASSANDRA-20736 at 7/2/26 1:06 PM:
---------------------------------------------------------------------

-Patch is included with CASSANDRA-20476 here: [4613|https://github.com/apache/cassandra/pull/4613]-


was (Author: beobal):
Patch is included with CASSANDRA-20476 here: [4613|https://github.com/apache/cassandra/pull/4613]

> Add CMS membership as a field in ClusterMetadata
> ------------------------------------------------
>
>                 Key: CASSANDRA-20736
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20736
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Cluster/Membership
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>             Fix For: 6.x
>
>
> Rather than inferring membership of the CMS from the DataPlacement for keyspaces with MetaStrategy replication, the membership should be explicitly encoded in ClusterMetadata. That DataPlacement can then be calculated from it and we can ensure that it isn't able to be modified directly by transformations.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org