[jira] [Commented] (CASSANDRA-7026) CQL:WHERE ... IN with full partition keys

["Benjamin Lerer (JIRA)" <ji...@apache.org>]

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

Benjamin Lerer commented on CASSANDRA-7026:
-------------------------------------------

Adding support for {{token(a) IN (token(1), token(2))}} will require that we modify {{StorageProxy}} to allow queries for multiple partition key ranges. This change is not a minor one.

As this patch is mostly for "convenience", I really do not think that it worths the trouble of doing that modification.


> CQL:WHERE ... IN with full partition keys
> -----------------------------------------
>
>                 Key: CASSANDRA-7026
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7026
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Core
>            Reporter: Dan Hunt
>            Assignee: Benjamin Lerer
>            Priority: Minor
>              Labels: cql
>
> It would be handy to be able to pass in a list of fully qualified composite partition keys in an IN filter to retrieve multiple distinct rows with a single select.  Not entirely sure how that would work.  It looks like maybe it could be done with the existing token() function, like:
> SELECT * FROM table WHERE token(keyPartA, keyPartB) IN (token(1, 1), token(4, 2))
> Though, I guess you'd also want some way to pass a list of tokens to a prepared statement through the driver.  This of course all assumes that an IN filter could be faster than a bunch of prepared statements, which might not be true.



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