[
https://issues.apache.org/jira/browse/CASSANDRA-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633424#comment-13633424
]
Pierre Chalamet commented on CASSANDRA-4210:
--------------------------------------------
This is still a problem when trying to bind an IN parameter for prepared
statement even in 1.2.4. For what I've seen, the column spec returned after
preparing
{code}
select * from Town where key in (?)
{code}
just tells that the parameter is of type 'key', not a set of type 'key'.
This would be really nice for binary protocol driver to know they could bind a
set of value for such parameter (and I'm pretty sure this info is known when
the statement is prepared).
> Support for variadic parameters list for "in clause" in prepared cql query
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-4210
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4210
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1.0
> Environment: prepared cql queries
> Reporter: Pierre Chalamet
> Priority: Minor
>
> This query
> {code}
> select * from Town where key in (?)
> {code}
> only allows one parameter for '?'.
> This means querying for 'Paris' and 'London' can't be executed in one step
> with this prepared statement.
> Current workarounds are:
> * either execute the prepared query 2 times with 'Paris' then 'London'
> * or prepare a new query {{select * from Town where key in (?, ?)}} and bind
> the 2 parameters
> Having a support for variadic parameters list with in clause could improve
> performance:
> * single hop to get the data
> * // fetching server side
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
