[jira] [Commented] (CASSANDRA-9857) Deal with backward compatibilty issue of broken AbstractBounds serialization

["Sylvain Lebresne (JIRA)" <ji...@apache.org>]

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

Sylvain Lebresne commented on CASSANDRA-9857:
---------------------------------------------

So, as pointed by [~bdeggleston] in CASSANDRA-9893, the backward compatibility tests from CASSANDRA-9704 does allow to expose this problem. So I've pushed a branch [here|https://github.com/pcmanus/cassandra/commits/9857] with a fix for this (which turns out not too hard). I've validated locally that this was fixing the {{large_count_test}} from Tyler's CASSANDRA-9704 tests in particular.

As a side note, on CASSANDRA-9893, Blake attributes the failure of {{static_columns_with_distinct_test}} to this, but I don't think that it's the case. I'm investigating what the real cause is and will followup on CASSANDRA-9393 but in any case, the patch here does fix the legitimate bug this ticket is about.

> 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)