[jira] [Updated] (CASSANDRA-10271) ORDER BY should allow skipping equality-restricted clustering columns

["Tyler Hobbs (JIRA)" <ji...@apache.org>]

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

Tyler Hobbs updated CASSANDRA-10271:
------------------------------------
    Description: 
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 = 0 AND b = 0 ORDER BY c ASC;
{noformat}

Currently, this results in the following error:

{noformat}
[Invalid query] message="Order by currently only support the ordering of 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 = 0 AND b = 0 ORDER BY b ASC, c ASC;
{noformat}

  was:
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 = 0 AND b = 0 ORDER BY c ASC;
{noformat}

Currently, this results in the following error:

{noformat}
[Invalid query] message="Order by currently only support the ordering of 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.


> ORDER BY should allow skipping equality-restricted clustering columns
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-10271
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10271
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API, Core
>            Reporter: Tyler Hobbs
>            Priority: Minor
>             Fix For: 3.x, 2.2.x
>
>
> 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 = 0 AND b = 0 ORDER BY c ASC;
> {noformat}
> Currently, this results in the following error:
> {noformat}
> [Invalid query] message="Order by currently only support the ordering of 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 = 0 AND b = 0 ORDER BY b ASC, c ASC;
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)