[
https://issues.apache.org/jira/browse/CASSANDRA-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899508#comment-13899508
]
Tyler Hobbs commented on CASSANDRA-4911:
----------------------------------------
Thanks for adding the dtest.
If I change the third-to-last test from
{noformat}
assert_all(cursor, "SELECT v FROM test WHERE k=0 AND c1 = 0 AND c2 IN (2, 0)
ORDER BY c1 ASC", [[2], [0]])
{noformat}
to
{noformat}
assert_all(cursor, "SELECT v FROM test WHERE k=0 AND c1 = 0 AND c2 IN (2, 0)
ORDER BY c1 DESC", [[2], [0]])
{noformat}
The query returns no results.
> 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)
