cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7026) CQL:WHERE ... IN with full partition keys
Date Mon, 04 Aug 2014 12:58:12 GMT

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

Sylvain Lebresne commented on CASSANDRA-7026:
---------------------------------------------

bq. This of course all assumes that an IN filter could be faster than a bunch of prepared
statements

It's not in practice so I'm not sure it worth bothering with this (though if someone comes
up with a patch and it's not too big, I have no particular supporting the syntax for "convenience").

> 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
>            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.2#6252)

Mime
View raw message