[
https://issues.apache.org/jira/browse/CASSANDRA-19270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807146#comment-17807146
]
Stefan Miklosovic commented on CASSANDRA-19270:
-----------------------------------------------
I backported that test to 4.0 (1) and two tests fail there:
compositeValueClustering and compositeValuePk, the latter fails on
{code}
java.lang.AssertionError:
Expecting a root cause with message:
<"Key length of 65554 is longer than maximum of 65535">
but message was:
<"Key length of 65560 is longer than maximum of 65535">.
Throwable that failed the check:
com.datastax.driver.core.exceptions.InvalidQueryException: Key length of 65560
is longer than maximum of 65535
{code}
(1)
https://github.com/smiklosovic/cassandra/commit/cea90ebd3aef09ae09cdd69fd218bb6baebcc3c1
I think that you are right that this is a problem in 4.x but this is fixed in
5.0.
I wonder how complicated it would be to fix this in 4.x as well ...
> Incorrect error type on oversized compound partition key
> --------------------------------------------------------
>
> Key: CASSANDRA-19270
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19270
> Project: Cassandra
> Issue Type: Bug
> Reporter: Nadav Har'El
> Priority: Normal
>
> Cassandra limits key lengths (partition and clustering) to 64 KB. If a user
> attempts to INSERT data with a partition key or clustering key exceeding that
> size, the result is a clear InvalidRequest error with a message like "{{{}Key
> length of 66560 is longer than maximum of 65535{}}}".
> There is one exception: If you have a *compound* partition key (i.e., two or
> more partition key components) and attempt to write one of them larger than
> 64 KB, then instead of an orderly InvalidRequest like you got when there was
> just one component, now you get a NoHostAvailable with the message:
> "{{{}error("'H' format requires 0 <= number <= 65535")}){}}}". This is not
> only uglier, it can also confuse the Cassandra driver to retry this request -
> because it doesn't realize that the request itself is broken and there is no
> point to repeat it.
> Interestingly, if there are multiple clustering key columns, this problem
> doesn't happen: we still get a nice InvalidRequest if any one of these is
> more than 64 KB.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
