cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-7855) Genralize use of IN for compound partition keys
Date Mon, 01 Sep 2014 09:36:20 GMT
Sylvain Lebresne created CASSANDRA-7855:

             Summary: Genralize use of IN for compound partition keys
                 Key: CASSANDRA-7855
             Project: Cassandra
          Issue Type: Bug
            Reporter: Sylvain Lebresne
            Priority: Minor
             Fix For: 2.0.11

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:
    k1 int,
    k2 int,
    v int,
    PRIMARY KEY ((k1, k2))
we allow
SELECT * FROM foo WHERE k1 = 0 AND k2 IN (1, 2)
but not
SELECT * FROM foo WHERE k1 IN (0, 1) AND k2 IN (1, 2)
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 necessary a better idea than parallelizing
queries server side so this syntax, when introduced, should probably be used sparingly, but
give 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

View raw message