[
https://issues.apache.org/jira/browse/CASSANDRA-9857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729166#comment-14729166
]
Blake Eggleston commented on CASSANDRA-9857:
--------------------------------------------
Thanks. That's pretty much what I had in mind. Agreed that the test isn't
really necessary to demonstrate the fix, but the time it takes to write the
test is much less than the time the test will save tracking down any
regressions with it.
> Deal with backward compatibilty issue of broken AbstractBounds serialization
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-9857
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9857
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 3.0 beta 2
>
>
> This ticket is related to CASSANDRA-9856 and CASSANDRA-9775. Even if the
> broken/incomplete serialization of {{AbstractBounds}} is not a problem per-se
> for pre-3.0 versions, it's still a problem for trunk and even though it's
> fixed by CASSANDRA-9775 for 3.0 nodes, it might be a problem for 3.0 nodes
> talking to older nodes.
> As the paging tests where those that exposed the problem (on trunk) in the
> first place, it would be nice to modify said paging tests to work on mixed
> version clustering so we can valid if it is a problem. If it is, then we'll
> probably have to add redundant checks on trunk so they ignore anything the
> 3.0 node sends incorrectly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
