[
https://issues.apache.org/jira/browse/CASSANDRA-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-8613:
--------------------------------------
Attachment: CASSANDRA-8613-trunk.txt
CASSANDRA-8613-2.1.txt
CASSANDRA-8613-2.0.txt
The patches for 2.0 and 2.1 fix the problem in {{SelectStatement.buildBound}}
and add some unit tests for the {{buildBound}} method in
{{SelectStatementTest}} as well as in {{MultiColumnRelationTest}}.
The patch for trunk modify the Restriction hierachy and converts
{{SingleColumnPrimaryKeyRestrictions}} into {{PrimaryKeyRestrictionSet}} which
support mix of {{SingleColumnRestriction}} and {{MultiColumnRestriction}}.
> 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
>
> Attachments: CASSANDRA-8613-2.0.txt, CASSANDRA-8613-2.1.txt,
> CASSANDRA-8613-trunk.txt
>
>
> 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)
