cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Constance Eustace (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-7054) Enable allow filtering IN clause on compound cluster key
Date Fri, 18 Apr 2014 15:15:16 GMT
Constance Eustace created CASSANDRA-7054:
--------------------------------------------

             Summary: Enable allow filtering IN clause on compound cluster key
                 Key: CASSANDRA-7054
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7054
             Project: Cassandra
          Issue Type: New Feature
          Components: API
            Reporter: Constance Eustace


Partition Key is P

Cluster Key is C1, C2, C3

If you are allowed to do:

SELECT P,C1,C2,C3 FROM table WHERE C1 = ? ALLOW FILTERING

Why can't we do:

SELET P,C1,C2,C3 FROM table WHERE C1 IN ('001','002','003) ALLOW FILTERING?

Is there a fundamental theoretical issue with that? I assume ALLOW FILTERING is applying the
where clause after the SELECT P1,C1,C2,C3 initial retrieval has occurred for the single-property
equality clause, so an IN clause wouldn't be much different... 

I'm also assuming there is substantial network savings of issuing the general query to CASSANDRA
rather than pelting the server with multiple requests.




--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message