Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 24 Jul 2017 09:38:00 +0000 (UTC)
From: =?utf-8?Q?Andr=C3=A9s_de_la_Pe=C3=B1a_=28JIRA=29?= <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12861961.1441402184000.313957.1500889080259@Atlassian.JIRA>
In-Reply-To: <JIRA.12861961.1441402184000@Atlassian.JIRA>
References: <JIRA.12861961.1441402184000@Atlassian.JIRA> <JIRA.12861961.1441402184301@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CASSANDRA-10271) ORDER BY should allow skipping
 equality-restricted clustering columns
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Mon, 24 Jul 2017 09:38:06 -0000


    [ https://issues.apache.org/jira/browse/CASSANDRA-10271?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D16098146#comment-16098146 ]=20

Andr=C3=A9s de la Pe=C3=B1a commented on CASSANDRA-10271:
-----------------------------------------------

Thanks for both reviewing and committing :)

> ORDER BY should allow skipping equality-restricted clustering columns
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-10271
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1027=
1
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL
>            Reporter: Tyler Hobbs
>            Assignee: Andr=C3=A9s de la Pe=C3=B1a
>            Priority: Minor
>             Fix For: 4.0
>
>         Attachments: 10271-3.x.txt, cassandra-2.2-10271.txt
>
>
> Given a table like the following:
> {noformat}
> CREATE TABLE foo (a int, b int, c int, d int, PRIMARY KEY (a, b, c));
> {noformat}
> We should support a query like this:
> {noformat}
> SELECT * FROM foo WHERE a =3D 0 AND b =3D 0 ORDER BY c ASC;
> {noformat}
> Currently, this results in the following error:
> {noformat}
> [Invalid query] message=3D"Order by currently only support the ordering o=
f columns following their declared order in the PRIMARY KEY"
> {noformat}
> However, since {{b}} is restricted by an equality restriction, we shouldn=
't require it to be present in the {{ORDER BY}} clause.
> As a workaround, you can use this query instead:
> {noformat}
> SELECT * FROM foo WHERE a =3D 0 AND b =3D 0 ORDER BY b ASC, c ASC;
> {noformat}


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org