[
https://issues.apache.org/jira/browse/CASSANDRA-13462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Jefferson updated CASSANDRA-13462:
-----------------------------------------
Comment: was deleted
(was: cqlsh> select * from dev.testinguuids where pk=6 ORDER BY ck ;
pk | ck | val
----+--------------------------------------+-----
6 | 10000000-0000-0200-0000-000000000000 | 1
6 | 20000000-0000-0200-0000-000000000000 | 1
6 | 10000000-0000-1200-0000-000000000000 | 1
6 | 20000000-0000-1200-0000-000000000000 | 1
6 | 10000000-0000-2200-0000-000000000000 | 1
6 | 20000000-0000-2200-0000-000000000000 | 1)
> 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)
