cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-525) use "pending ranges" abstraction in TokenMetadata
Date Sat, 07 Nov 2009 12:34:32 GMT


Hudson commented on CASSANDRA-525:

Integrated in Cassandra #251 (See [])
    containing isBootstrapping and BootstrapTokenAddress information in TokenMetadata is the
wrong level of abstraction.  Switch to pendingRanges instead.
patch by jbellis and Jaakko Laine for 
split out onJoin from onChange, so we can pass a single ApplicationState object to onChange
to emphasize that it gets called once per AS; rename ApplicationState.getState -> getValue
patch by jbellis; reviewed by Jaakko Laine for 
make sortedtokens passably efficient
patch by jbellis; reviewed by Jaakko Laine for 
fix TODO in tokenmetadata (bootstrap tokens aren't part of the official ring now).  r/m redundant
getNextEndPoint method in favor of getSuccessor
patch by jbellis; reviewed by Jaakko Laine for 

> use "pending ranges" abstraction in TokenMetadata
> -------------------------------------------------
>                 Key: CASSANDRA-525
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.5
>         Attachments: 0001-CASSANDRA-525-cleanup.txt, 0002-make-sortedtokens-passably-efficient.txt,
0003-containing-isBootstrapping-and-BootstrapTokenAddress-i.txt, 0003-split-out-onJoin-from-onChange-so-we-can-pass-a-singl.txt,
0004-containing-isBootstrapping-and-BootstrapTokenAddress-i.txt, 0004-use-bootstrap_node-in-bootsrapping.txt,

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message