[
https://issues.apache.org/jira/browse/CASSANDRA-15201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benedict updated CASSANDRA-15201:
---------------------------------
Fix Version/s: 3.0.19
Source Control Link:
[d50ec52d6e6c9140080c86fcff08b3cd37a6ca3d|http://github.com/apache/cassandra/commit/d50ec52d6e6c9140080c86fcff08b3cd37a6ca3d]
Since Version: 3.0.0
Status: Resolved (was: Ready to Commit)
Resolution: Fixed
bq. Maybe the new checks could throw IllegalArgumentException rather than
RuntimeException
Thanks. I had considered introducing a new exception type to capture the
situation before, but IAE works probably better than RE at least.
> LegacyLayout does not handle paging states that cross a collection column
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-15201
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15201
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Internode
> Reporter: Benedict
> Assignee: Benedict
> Priority: Normal
> Fix For: 3.0.19
>
>
> {{LegacyLayout.decodeBound}} assumes there is only a single extra component,
> referring to a column name. In fact an encoded page boundary may include a
> collection column, and this occurs as a matter of course when paging a table
> whose last column is a collection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
