cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Michallat (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-13193) PK indices in 'Prepared' response can overflow
Date Tue, 07 Feb 2017 18:00:45 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-13193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Olivier Michallat resolved CASSANDRA-13193.
-------------------------------------------
       Resolution: Duplicate
    Reproduced In: 3.9, 3.0.0  (was: 3.0.0, 3.9)

JIRA glitch created this duplicate of CASSANDRA-13192, sorry.

> PK indices in 'Prepared' response can overflow
> ----------------------------------------------
>
>                 Key: CASSANDRA-13193
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13193
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Olivier Michallat
>            Priority: Minor
>
> CASSANDRA-7660 added PK indices to the {{Prepared}} response. They are encoded as shorts.
> It's possible to prepare a query with more than 32768 placeholders (the hard limit is
64K). For example, we sometimes see users running IN queries with thousands of elements (a
bad practice of course, but still possible).
> When a PK component is present after the 32768th position, the PK index overflows and
a negative value is returned. This can throw off clients if they're not prepared to handle
it. For example, the Java driver currently accepts the response, but will fail much later
if you try to compute a bound statement's routing key.
> Failing fast would be safer here, the prepare query should error out if we detect a PK
index overflow.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message