[
https://issues.apache.org/jira/browse/CASSANDRA-7020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711852#comment-14711852
]
Piotr Kołaczkowski commented on CASSANDRA-7020:
-----------------------------------------------
"Note though that in the case where startToken or endToken is the minimum
token, then
this special case rule should not apply."
[~marcus_d] any thoughts why this special case was not applied before? The
patch looks good, but I wonder what else relied on returning everything when
startToken or endToken was minimum token.
> Incorrect result of query WHERE token(key) < -9223372036854775808 when using
> Murmur3Partitioner
> -----------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-7020
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7020
> Project: Cassandra
> Issue Type: Bug
> Environment: cassandra 2.0.6-snapshot
> Reporter: Piotr Kołaczkowski
> Assignee: Marko Denda
> Fix For: 2.0.x
>
> Attachments: 7020.txt
>
>
> {noformat}
> cqlsh:test1> select * from test where token("key") < -9223372036854775807;
> (0 rows)
> cqlsh:test1> select * from test where token("key") < -9223372036854775808;
> key | value
> -----+----------
> 5 | eeeeee
> 10 | j
> 1 | aaaa
> 8 | hhhhhhhh
> 2 | bbb
> 4 | dd
> 7 | gggg
> 6 | fff
> 9 | iiii
> 3 | ccccc
> {noformat}
> Expected: empty result.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
