cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8230) LongToken no longer needs to use a boxed Long
Date Tue, 04 Nov 2014 16:20:34 GMT

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

Sam Tunnicliffe commented on CASSANDRA-8230:
--------------------------------------------

I would argue that it is worth preserving, being able to access the token values themselves
is pretty useful (for us, especially in the indexing case I mentioned) and adding {{getTokenValue()}}
hopefully won't add too many complications down the line.

> LongToken no longer needs to use a boxed Long
> ---------------------------------------------
>
>                 Key: CASSANDRA-8230
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8230
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Branimir Lambov
>            Assignee: Branimir Lambov
>            Priority: Minor
>             Fix For: 2.1.2
>
>         Attachments: 8230-2.1.patch
>
>
> After CASSANDRA-8171 a token reference field is no longer a requirement for tokens. This
permits LongTokens to include a primitive long field, which should noticeably improve the
space and time efficiency of the Murmur3Partitioner tokens.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message