Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 29 Jan 2015 09:32:35 +0000 (UTC)
From: "Benjamin Lerer (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12738229.1409564166000.203420.1422523955469@Atlassian.JIRA>
In-Reply-To: <JIRA.12738229.1409564166000@Atlassian.JIRA>
References: <JIRA.12738229.1409564166000@Atlassian.JIRA>
 <JIRA.12738229.1409564166834@arcas>
Subject: [jira] [Updated] (CASSANDRA-7855) Genralize use of IN for compound
 partition keys
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benjamin Lerer updated CASSANDRA-7855:
--------------------------------------
    Fix Version/s:     (was: 2.1.3)
                   3.0

> Genralize use of IN for compound partition keys
> -----------------------------------------------
>
>                 Key: CASSANDRA-7855
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7855
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Benjamin Lerer
>            Priority: Minor
>              Labels: cql
>             Fix For: 3.0
>
>
> When you have a compount partition key, we currently only support to have a {{IN}} on the last column of that partition key. So given:
> {noformat}
> CREATE TABLE foo (
>     k1 int,
>     k2 int,
>     v int,
>     PRIMARY KEY ((k1, k2))
> )
> {noformat}
> we allow
> {noformat}
> SELECT * FROM foo WHERE k1 = 0 AND k2 IN (1, 2)
> {noformat}
> but not
> {noformat}
> SELECT * FROM foo WHERE k1 IN (0, 1) AND k2 IN (1, 2)
> {noformat}
> There is no particular reason for us not supporting the later (to the best of my knowledge) since it's reasonably straighforward, so we should fix it.
> I'll note that using {{IN}} on a partition key is not necessarily a better idea than parallelizing queries server client side so this syntax, when introduced, should probably be used sparingly, but given we do support IN on partition keys, I see no reason not to extend it to compound PK properly.


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