cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-4760) CQL3 equality is broken when using composites and clustering order by
Date Wed, 03 Oct 2012 22:05:14 GMT
T Jake Luciani created CASSANDRA-4760:
-----------------------------------------

             Summary: CQL3 equality is broken when using composites and clustering order by
                 Key: CASSANDRA-4760
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4760
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: T Jake Luciani
             Fix For: 1.1.6


The following query is broken when you specify the second order by

{code}
cqlsh:dev> DROP TABLE testrev ;
cqlsh:dev> CREATE TABLE testrev (
       ...          key text,
       ...          rdate timestamp,
       ...          rdate2 timestamp,
       ...          num double,
       ...          PRIMARY KEY(key,rdate,rdate2)
       ...          ) WITH COMPACT STORAGE
       ...          AND CLUSTERING ORDER BY(rdate DESC, rdate2 DESC);
cqlsh:dev> INSERT INTO testrev(key,rdate,rdate2,num) VALUES ('foo','2012-01-01','2012-01-01',10.5);
cqlsh:dev> select * from testrev where key='foo' and rdate = '2012-01-01';
Bad Request: Range finish must come after start in traversal order
Perhaps you meant to use CQL 2? Try using the -2 option when starting cqlsh.
cqlsh:dev> 
{code}

--
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