cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4550) nodetool ring output should use hex not integers for tokens
Date Fri, 09 Nov 2012 18:32:12 GMT

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

Brandon Williams commented on CASSANDRA-4550:
---------------------------------------------

I'm not sure this is useful with m3p, either, since we now have negative tokens.
                
> nodetool ring output should use hex not integers for tokens
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-4550
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4550
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>         Environment: Linux
>            Reporter: Aaron Turner
>            Assignee: Kirk True
>            Priority: Trivial
>              Labels: lhf
>         Attachments: trunk-4550.txt
>
>
> The current output of nodetool ring prints start token values as base10 integers instead
of hex.  This is not very user friendly for a number of reasons:
> 1. Hides the fact that the values are 128bit
> 2. Values are not of a consistent length, while in hex padding with zero is generally
accepted
> 3. When using the default random partitioner, having the values in hex makes it easier
for users to determine which node(s) a given key resides on since md5 utilities like md5sum
output hex.

--
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: http://www.atlassian.com/software/jira

Mime
View raw message