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

Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/10/04 17:29:00 UTC

[jira] [Commented] (GEODE-5815) Find an effective way to test DataSerializable's backward compatibility

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

ASF subversion and git services commented on GEODE-5815:
--------------------------------------------------------

Commit b2248deea8305808949090a4a346c9a202b2ad46 in geode's branch refs/heads/develop from jinmeiliao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b2248de ]

GEODE-5815: ignore testDataSerializable for java9 and above (#2491)



> Find an effective way to test DataSerializable's backward compatibility
> -----------------------------------------------------------------------
>
>                 Key: GEODE-5815
>                 URL: https://issues.apache.org/jira/browse/GEODE-5815
>             Project: Geode
>          Issue Type: Improvement
>          Components: core, tests
>            Reporter: Jinmei Liao
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> current  AnalyzeSerializablesJUnitTestBase.testDataSerializable is only trying to check if someone accidentally changed the implementation of fromData and toData of a declared list of DataSerializable classes. This is not sufficient. We need a way to test that the on-wire/on-file form of the object from an older version can still be deserialized correctly using the current version.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)