[
https://issues.apache.org/jira/browse/CASSANDRA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605007#comment-13605007
]
Sylvain Lebresne commented on CASSANDRA-5355:
---------------------------------------------
I note that 64k might sound arbitrary low and we might want to lift the
limitation. However, as said above, for sets elements we are constrained by the
current internal column name size. We could of course lift that limitation, but
it's not trivial. Of course, we could lift the limitation only for map and list
values, but even that would unfortunately break the current format currently
used to send collections to the client, so at a minimum it would require a
binary protocol version bump.
> Collection values size is not validated.
> ----------------------------------------
>
> Key: CASSANDRA-5355
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5355
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Minor
>
> Collections values are currently limited to 64K because the serialized form
> used uses shorts to encode the elements length (and for sets elements and key
> map, because they are part of the internal column name that is itself limited
> to 64K).
> However, there is no check on the collection elements size currently so we
> don't refuse values > 64K (except for sets elements and map keys because we
> check internal column name sizes), even though they can't be decoded
> correctly client 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
