[ https://issues.apache.org/jira/browse/CASSANDRA-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-3892: -------------------------------------- Reviewer: thepaul > improve TokenMetadata abstraction, naming - audit current uses > -------------------------------------------------------------- > > Key: CASSANDRA-3892 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3892 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Peter Schuller > Assignee: Peter Schuller > Attachments: CASSANDRA-3892-draft-v2.txt, > CASSANDRA-3892-draft-v3.txt, CASSANDRA-3892-draft-v4.txt, > CASSANDRA-3892-draft.txt, CASSANDRA-3892-split-001-change-naming.txt, > CASSANDRA-3892-split-002-make-moving-endpoints-a-map.txt, > CASSANDRA-3892-split-003-remove-redundant-comment.txt, > CASSANDRA-3892-split-004-add-assertion-when-declaring-leaving-endpoint.txt, > CASSANDRA-3892-split-005-add-assertion-when-declaring-moving-endpoint.txt, > CASSANDRA-3892-split-006-do-not-forget-nuking-in-moving-when-removing-endpoint.txt, > CASSANDRA-3892-split-007-tokenmetadata-comments.txt, > CASSANDRA-3892-split-008-make-firsttokenindex-private.txt, > CASSANDRA-3892-split-009-storageservice-comments.txt > > > CASSANDRA-3417 has some background. I want to make the distinction more clear > between looking at the ring from different perspectives (reads, writes, > others) and adjust naming to be more clear on this. I also want to go through > each use case and try to spot any subtle pre-existing bugs that I almost > introduced in CASSANDRA-3417, had not Jonathan caught me. > I will submit a patch soonish. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira