[
https://issues.apache.org/jira/browse/CASSANDRA-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204129#comment-13204129
]
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: https://issues.apache.org/jira/browse/CASSANDRA-2917
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
