cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-3892) improve TokenMetadata abstraction, naming - audit current uses
Date Tue, 09 Jul 2013 16:25:54 GMT


Jonathan Ellis resolved CASSANDRA-3892.

    Resolution: Won't Fix

Oops, looks like Paul dropped this on the floor and I didn't notice because it wasn't marked
Patch Available.  Suspect this is substantially obsolete after the rewrite done in CASSANDRA-3881.
> improve TokenMetadata abstraction, naming - audit current uses
> --------------------------------------------------------------
>                 Key: CASSANDRA-3892
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Peter Schuller
>            Assignee: Peter Schuller
>         Attachments: CASSANDRA-3892-draft.txt, CASSANDRA-3892-draft-v2.txt, CASSANDRA-3892-draft-v3.txt,
CASSANDRA-3892-draft-v4.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-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
For more information on JIRA, see:

View raw message