[
https://issues.apache.org/jira/browse/CASSANDRA-15201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-15201:
----------------------------------------
Status: Ready to Commit (was: Review In Progress)
+1
Maybe the new checks could throw {{IllegalArgumentException}} rather than
{{RuntimeException}}, but obviously this doesn't make any difference
functionally, so I don't object if you prefer the way it is.
> 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
>
> {{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]
