[
https://issues.apache.org/jira/browse/CASSANDRA-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-4911:
----------------------------------------
Attachment: 6701_rebased.txt
That last bit is actually not really related to this ticket/patch but is rather
an old (relatively harmless) bug and I've opened CASSANDRA-6701 for that. I'm
attaching a rebase of the CASSANDRA-6701 patch to 2.1 here for testing purposes
but that issue should really be handled in it's own ticket.
> 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, 6701_rebased.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)
