[
https://issues.apache.org/jira/browse/CASSANDRA-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288158#comment-14288158
]
Benjamin Lerer commented on CASSANDRA-8613:
-------------------------------------------
The reason, I think, while it is not cover is that we never intended to support
this type of query. It is a side effect of how multi-column relations were
originally developed. In the following versions we implemented some check to
prevent the mix of single column and multi column relation on the clustering
keys. The refactoring of {{SelectStatement}} in CASSANDRA-7981 has enforced
even more that constraint in the code.
Overall, I agree with [~thobbs] that this query make sense and that we should
support it. It is just not an easy thing to do on the current code.
> Regression in mixed single and multi-column relation support
> ------------------------------------------------------------
>
> Key: CASSANDRA-8613
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8613
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Tyler Hobbs
> Assignee: Benjamin Lerer
> Fix For: 2.1.3, 2.0.13
>
>
> In 2.0.6 through 2.0.8, a query like the following was supported:
> {noformat}
> SELECT * FROM mytable WHERE clustering_0 = ? AND (clustering_1, clustering_2)
> > (?, ?)
> {noformat}
> However, after CASSANDRA-6875, you'll get the following error:
> {noformat}
> Clustering columns may not be skipped in multi-column relations. They should
> appear in the PRIMARY KEY order. Got (c, d) > (0, 0)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
