[
https://issues.apache.org/jira/browse/CASSANDRA-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212199#comment-14212199
]
Sylvain Lebresne commented on CASSANDRA-4210:
---------------------------------------------
I strongly suspect that the first error is actually due to the nodejs driver.
Most probably, the nodejs driver doesn't have enough type information in the
non-prepared case to properly serialize your uuid as a uuid. Instead, it
probably serialize it as a string which is incorrect. You should report this to
the nodejs driver authors to figure this out, but the error pretty clearly
indicate that something wrong has been sent to the server and that's almost
surely not a server bug.
Regarding the 2nd case, you do not provided any information to assert that the
query should indeed have returned two rows. Maybe you're 2nd UUID actually
doesn't exist in the DB and the answer is correct. Or, here again, maybe this
is a nodejs driver bug. Because we have a fair amount tests for IN queries so
the likeliness of a server not returning the proper data is not extremely high
a priori. Overall I suggest that 1) you double-check that your query should
indeed return 2 rows, 2) if it should indeed that you first report it to the
nodejs driver to see if it's not a nodejs driver bug and 3) if it does turn out
that it's likely a server bug, that you open a new separate ticket with a bit
more information on your case (like at least the Cassandra version in use) and
full reproduction steps if possible.
> 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
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 2.0.1
>
> Attachments: 4210.txt
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
