cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Michallat (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8276) Unusable prepared statement with 65k parameters
Date Fri, 07 Nov 2014 15:32:33 GMT


Olivier Michallat commented on CASSANDRA-8276:

I might add that we are aware that preparing a statement with 65535 parameters is a ridiculous
idea. However, the protocol allows it, and if the statement is generated through some kind
of abstraction layer, I can see how this could get misused (for instance, with IN statements).

If that many parameters cause some sort of exhaustion server-side, we could force a more sensible
limit driver-side.

> Unusable prepared statement with 65k parameters
> -----------------------------------------------
>                 Key: CASSANDRA-8276
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Cassandra 2.0.10
> Java driver 2.0.8-SNAPSHOT
>            Reporter: Pierre Laporte
> We had an issue ([JAVA-515|]) in the
java-driver when the number of parameters in a statement is greater than the supported limit
> I added a limit-test to verify that prepared statements with 65535 parameters were accepted
by the driver, but ran into an issue on the Cassandra side.
> Basically, the test runs forever, because the driver receives an inconsistent answer
from Cassandra.  When we prepare the statement, C* answers that it is correctly prepared,
however when we try to execute it, we receive a {{UNPREPARED}} answer.
> [Here is the code|]
to reproduce the issue.

This message was sent by Atlassian JIRA

View raw message