You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jon Haddad (Jira)" <ji...@apache.org> on 2025/02/27 23:16:00 UTC
[jira] [Moved] (CASSANALYTICS-11) Internals are unaware that Cassandra can have multiple tokens
[ https://issues.apache.org/jira/browse/CASSANALYTICS-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jon Haddad moved CASSANDRA-19608 to CASSANALYTICS-11:
-----------------------------------------------------
Component/s: (was: Analytics Library)
Impacts: (was: None)
Key: CASSANALYTICS-11 (was: CASSANDRA-19608)
Platform: (was: All)
Project: Apache Cassandra Analytics (was: Apache Cassandra)
> Internals are unaware that Cassandra can have multiple tokens
> -------------------------------------------------------------
>
> Key: CASSANALYTICS-11
> URL: https://issues.apache.org/jira/browse/CASSANALYTICS-11
> Project: Apache Cassandra Analytics
> Issue Type: Sub-task
> Reporter: Jon Haddad
> Priority: Normal
>
> The internal Partitioner, CassandraRing, CassandraInstance (and probably others) is unaware that a node can have many tokens. There are many references and assumptions throughout the codebase that a node will have a single token. Updating these from a simple String in CassanraInstance to a SortedSet<String> appears to be the first step to supporting multiple tokens per node.
> This body of work is purely to update the plumbing between the various classes to pay off the technical debt of the assumption that a node can only have a single token.
--
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