cassandra-commits mailing list archives

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

     [ https://issues.apache.org/jira/browse/CASSANDRA-13462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne resolved CASSANDRA-13462.
------------------------------------------
    Resolution: Won't Fix

I'm sorry this isn't working as you expected it, but it is the way it works (and has been
working for years) and we can't change that without breaking every user that uses UUID ever
which is obviously out of question.

> 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