[jira] [Resolved] (GEODE-73) Remove old rolling-upgrade methods and code

["Bruce Schuchardt (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GEODE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Schuchardt resolved GEODE-73.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0-incubating.M2

Fixed in http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/f7b2714c


> Remove old rolling-upgrade methods and code
> -------------------------------------------
>
>                 Key: GEODE-73
>                 URL: https://issues.apache.org/jira/browse/GEODE-73
>             Project: Geode
>          Issue Type: Improvement
>    Affects Versions: 1.0.0-incubating
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>              Labels: cleanup, docs
>             Fix For: 1.0.0-incubating.M2
>
>
> Geode supports rolling upgrade between major and minor versions.  This is a really cool feature that should be kept up, but there are a lot of serialization methods that are checking for old versions of GemFire in the code that ought to be removed.  These have the form
> toDataPre_GFE_major_minor_patch_build()
> fromDataPre_GFE_major_minor_patch_build()
> These methods are no longer needed since rolling upgrade isn't going to be possible from old GemFire processes to Geode.  Also, old GemFire clients won't be supported either due to the package renaming that needs to take place.
> Aside from these methods there are other places that are checking to see what version is attached to a DataInput or DataOutput using InternalDataSerializer.getVersionForDataStream[OrNull], or are using the getVersionObject() method in InternalDistributedMember to make decisions about how to deal with old GemFire members.  Care needs to be taken here since some uses of these methods are to set up proper serialization in HeapDataOutputStreams.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)