cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2917) expose calculate midrange for token in jmx
Date Wed, 08 Feb 2012 23:55:59 GMT


Jonathan Ellis commented on CASSANDRA-2917:

bq. I agree its very verbose and only went down that route as I saw them used in a few other
places in the codebase

Sorry about that. :)

bq. what's the best branch to work off when creating small patches like this

When in doubt, stick with trunk. In this case I'm comfortable committing to 1.1 as well since
it's pretty self-contained.
> expose calculate midrange for token in jmx
> ------------------------------------------
>                 Key: CASSANDRA-2917
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Jackson Chung
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>              Labels: lhf
>             Fix For: 1.1
>         Attachments: trunk-2917-1.txt, trunk-2917.txt
> currently there is no easy way to get midrange, especially for OPP. For simplicity, you
could call OrderPreservingPartitioner.midpoint(Token, Token), that gives you a rough estimate
(and you'd still need to remove non-utf8 characters.)
> A more accurate but difficult way is to sample the keys in that range and pick the midpoint
of those. We should expose that via jmx, because without this, supporting OPP w/o this is
quite challenging.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message