[jira] [Commented] (CASSANDRA-7054) Enable allow filtering IN clause on compound cluster key

["Constance Eustace (JIRA)" <ji...@apache.org>]

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

Constance Eustace commented on CASSANDRA-7054:
----------------------------------------------

Thanks. No idea why my search didn't find the original, I did many CASSANDRA in clause searches....

Why this is important to me: I'm writing an Entity-Attribute-Value layer and currently have to do JSON encoding for things, but this would enable me to do a more flexible/flat/accessible schema and as a HUGE bonus, make it easier to access the data through Presto / Spark / Hadoop etc without repository pattern overhead. 

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