[
https://issues.apache.org/jira/browse/CASSANDRA-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476786#comment-13476786
]
Sylvain Lebresne commented on CASSANDRA-4808:
---------------------------------------------
bq. I'm confused as to why we need negative tokens.
To elaborate, M3P uses a long token internally and since long in java are
signed, we end up with a tokens that can be negative. We could chose to
interpret the long as unsigned, but even if we do that, we need the minimum
token to not be a valid token, so tokens would have to be a value in [1,
2^64-1], not [0, 2^64-1] and so people would have to adapt whatever algorithm
they use to compute tokens anyway and hence I'm not sure it's worth bothering
changing from negative tokens.
> nodetool doesnt work well with negative tokens
> ----------------------------------------------
>
> Key: CASSANDRA-4808
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4808
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Vijay
> Assignee: Vijay
> Priority: Minor
> Fix For: 1.2.0 beta 1
>
> Attachments: 0001-CASSANDRA-4808.patch
>
>
> ./apache-cassandra-1.2.0-beta1-SNAPSHOT/bin/nodetool move
> \-2253536297082652573
> Unrecognized option: -2253536297082652573
> usage: java org.apache.cassandra.tools.NodeCmd --host <arg> <command>
>
> -cf,--column-family <arg> only take a snapshot of the specified column
> family
--
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
