You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2019/07/04 15:04:00 UTC

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

    [ https://issues.apache.org/jira/browse/CASSANDRA-15201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878730#comment-16878730 ] 

Benedict commented on CASSANDRA-15201:
--------------------------------------

On second thoughts, the dtest is of dubious value without a proper client connection to the old node, which we don't currently have very nice tooling for.  Perhaps we can follow-up, but I've removed the dtest for now.

> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org