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-4911) Lift limitation that order by columns must be selected for IN queries
Date Wed, 12 Feb 2014 09:06:20 GMT

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

Sylvain Lebresne updated CASSANDRA-4911:
----------------------------------------

    Attachment: 4911-v2.txt

Ok, the logic in that first patch was a bit confused. Attaching v2 that fixes that. I've also
pushed [a dtest|https://github.com/riptano/cassandra-dtest/blob/fa7d63092807bb9c2100d0608414082c4fe7a843/cql_tests.py#L3721-3744].

> Lift limitation that order by columns must be selected for IN queries
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-4911
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4911
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 2.1
>
>         Attachments: 4911-v2.txt, 4911.txt
>
>
> This is the followup of CASSANDRA-4645. We should remove the limitation that for IN queries,
you must have columns on which you have an ORDER BY in the select clause.
> For that, we'll need to automatically add the columns on which we have an ORDER BY to
the one queried internally, and remove it afterwards (once the sorting is done) from the resultSet.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message