Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 17 Dec 2013 16:07:16 +0000 (UTC)
From: "Sylvain Lebresne (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12614771.1352114234398.50751.1387296436942@arcas>
In-Reply-To: <JIRA.12614771.1352114234398@arcas>
References: <JIRA.12614771.1352114234398@arcas>
Subject: [jira] [Updated] (CASSANDRA-4911) Lift limitation that order by
 columns must be selected for IN queries
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

    Attachment: 4911.txt

Attaching patch on trunk for this. Since no-one complained about this so far and since it's slightly risky, let's target that to 2.1. We do need it a bit more in 2.1 following CASSANDRA-5417 (as explained in this ticket, we have one dtest failure otherwise). 

> 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
>    Affects Versions: 1.2.0 beta 1
>            Reporter: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 2.1
>
>         Attachments: 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.4#6159)