cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2917) expose calculate midrange for token in jmx
Date Tue, 19 Jul 2011 05:01:57 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067495#comment-13067495
] 

Jonathan Ellis commented on CASSANDRA-2917:
-------------------------------------------

Dealing with the non-utf8 characters is the responsibility of whoever calls this.  For most
cases I imagine you could just strip them out, or you could "round" to the nearest utf8.

All we want this ticket to do is expose the sampling Cassandra has, so we can do the rest
externally.

> expose calculate midrange for token in jmx
> ------------------------------------------
>
>                 Key: CASSANDRA-2917
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2917
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jackson Chung
>            Priority: Minor
>              Labels: lhf
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message