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] [Commented] (CASSANDRA-4936) Less than operator when comparing timeuuids behaves as less than equal.
Date Mon, 14 Jan 2013 09:44:14 GMT

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

Sylvain Lebresne commented on CASSANDRA-4936:
---------------------------------------------

bq. Perhaps minTimeUUID() and maxTimeUUID()?

Agreed, that's probably less confusing. That's trivial to change though, I'll change before
committing if it comes to that.

bq. are we carefully tracking changes to CQL by version and documenting them somewhere?

Not yet, but I do intend to do it now that CQL3 is final. It'll probably be listed in http://cassandra.apache.org/doc/cql3/CQL.html.
Though if that patch is committed, I'll also mention it clearly in the NEWS file.
                
> Less than operator when comparing timeuuids behaves as less than equal.
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-4936
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4936
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.0
>         Environment: Linux CentOS.
> Linux localhost.localdomain 2.6.18-308.16.1.el5 #1 SMP Tue Oct 2 22:01:37 EDT 2012 i686
i686 i386 GNU/Linux
>            Reporter: Cesar Lopez-Nataren
>            Assignee: Sylvain Lebresne
>             Fix For: 1.2.1
>
>         Attachments: 4936.txt
>
>
> If we define the following column family using CQL3:
> CREATE TABLE useractivity (
>   user_id int,
>   activity_id 'TimeUUIDType',
>   data text,
>   PRIMARY KEY (user_id, activity_id)
> );
> Add some values to it.
> And then query it like:
> SELECT * FROM useractivity WHERE user_id = '3' AND activity_id < '2012-11-07 18:18:22-0800'
ORDER BY activity_id DESC LIMIT 1;
> the record with timeuuid '2012-11-07 18:18:22-0800' returns in the results.
> According to the documentation, on CQL3 the '<' and '>' operators are strict, meaning
not inclusive, so this seems to be a bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message