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] [Updated] (CASSANDRA-4246) cql3 ORDER BY not ordering
Date Thu, 17 May 2012 12:45:07 GMT

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

Sylvain Lebresne updated CASSANDRA-4246:
----------------------------------------

    Attachment: 4246.txt

We were doing some validation that order by was not used when multiple internal rows are queried,
but only for the reversed case for some reason. Patch attached to fix (it also refuse order
by when a IN is used on the row key as this would require a bit more work to have it work
correctly).
                
> cql3 ORDER BY not ordering
> --------------------------
>
>                 Key: CASSANDRA-4246
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4246
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.0
>            Reporter: paul cannon
>            Assignee: Sylvain Lebresne
>              Labels: cql3
>         Attachments: 4246.txt
>
>
> Creating the simplest composite-key cql3 table I can think of, populating it with a few
rows of data, then trying to do a query with an ORDER BY does not yield ordered results.
> Here's a cql script:
> {noformat}
> create keyspace test with strategy_class = 'SimpleStrategy'
>    and strategy_options:replication_factor = 1;
> use test;
> create table moo (a int, b int, c int, primary key (a, b));
> insert into moo (a, b, c) values (123, 12, 3400);
> insert into moo (a, b, c) values (122, 13, 3500);
> insert into moo (a, b, c) values (124, 10, 3600);
> insert into moo (a, b, c) values (121, 11, 3700);
> select * from moo;
> select * from moo order by b;
> {noformat}
> Here is the output of those two queries:
> {noformat}
>  a   | b  | c
> -----+----+------
>  121 | 11 | 3700
>  122 | 13 | 3500
>  124 | 10 | 3600
>  123 | 12 | 3400
>  a   | b  | c
> -----+----+------
>  121 | 11 | 3700
>  122 | 13 | 3500
>  124 | 10 | 3600
>  123 | 12 | 3400
> {noformat}
> I also tried these using the bare thrift interface, to make sure it wasn't python-cql
or cqlsh doing something stupid. Same results. Am I totally missing something important here
about how this is supposed to work?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message