cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Jefferson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13462) Unexpected behaviour with range queries on UUIDs
Date Wed, 19 Apr 2017 12:43:41 GMT

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

Andrew Jefferson commented on CASSANDRA-13462:
----------------------------------------------

Thanks for the quick reply - Is this behaviour documented somewhere?

I think it would be quite a feat to find someone who was relying on this behaviour!



> Unexpected behaviour with range queries on UUIDs
> ------------------------------------------------
>
>                 Key: CASSANDRA-13462
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13462
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Andrew Jefferson
>
> My expectation is that UUIDs should behave as 128 bit integers for comparison.
> However it seems that the Cassandra implementation compares first the uuid version number,
then the remaining values of the uuid.
> e.g. in C*
>  10000000-0000-3000-0000-000000000000
>  is greater than 
> 20000000-0000-1000-0000-000000000000 
> (n.b. the 13th value is the uuid version)
>  - this is consistent across range queries and using ORDER BY 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message