cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jared Gray (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8613) Regression in mixed single and multi-column relation support
Date Mon, 26 Jan 2015 14:35:35 GMT

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

Jared Gray commented on CASSANDRA-8613:
---------------------------------------

I originally worked with Hobbs to open this issue. I've linked to a design document below,
describing our internal use of multi-column relations in Cassandra. Though all of these queries
worked in version 2.0.6, many have broken since Cassandra 2.0.9. 

[Paging and Filtering with Apache Cassandra|https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Wf96854c0c8fc_4762_9b83_c6247feca5fc/page/Paging%20and%20Filtering%20with%20Apache%20Cassandra]

> 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)

Mime
View raw message