cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8613) Regression in mixed single and multi-column relation support
Date Tue, 10 Mar 2015 03:00:48 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354185#comment-14354185
] 

Aleksey Yeschenko commented on CASSANDRA-8613:
----------------------------------------------

Relabeling as 2.0.14, since it's not in the currently being tested cassandra-2.0.13 branch
(we can cherry-pick it into cassandra-2.0.13 if we decide it's major enough, just updating
JIRA to reflect the current state).

> 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.0.13, 2.1.4
>
>         Attachments: 8613-2.0-v2.txt, 8613-2.1-v2.txt, 8613-trunk-v2.txt, 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)

Mime
View raw message