You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2015/01/29 11:39:34 UTC

[jira] [Commented] (CASSANDRA-8701) Allow multi-column restrictions on partition key compounds

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

Sylvain Lebresne commented on CASSANDRA-8701:
---------------------------------------------

I'll note that if it's not trivial to do with the current state of the code (haven't looked), I'm personally in favor of resolving that as "won't fix" or "later". Multi-partition queries are discouraged (since parallelizing client side is preferable) and while we want some support for IN on partition keys for the sake of parity with thrift multiget, I think that CASSANDRA-7855 is good enough for that purpose.

> Allow multi-column restrictions on partition key compounds
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-8701
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8701
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Benjamin Lerer
>            Assignee: Benjamin Lerer
>            Priority: Minor
>
> We would like to allow queries like:
> {code}SELECT * FROM foo WHERE (k1, k2) IN ( (0, 1) , (1, 2) ){code}
> were k1 and k2 are partition key compounds.



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