[CASSANDRA-15201] LegacyLayout does not handle paging states that cross a collection column

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.19
• Component/s: Messaging/Internode
• Bug Category: Correctness - Transient Incorrect Response
• Severity: Normal
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Since Version: 3.0.0

Source Control Link

d50ec52d6e6c9140080c86fcff08b3cd37a6ca3d

Test and Documentation Plan

Two unit tests included

• Assignee: Benedict Elliott Smith
• Reporter: Benedict Elliott Smith

Authors

Benedict Elliott Smith

Reviewers

Sam Tunnicliffe

• Created: 04/Jul/19 11:56
• Updated: 10/Jul/19 14:01
• Resolved: 10/Jul/19 14:01

Description

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.