You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Nabarun Nag <nn...@vmware.com> on 2021/03/11 18:48:37 UTC
[Poposal] Backport GEODE-9019 to Apache Geode 1.14.0 branch
Hi everyone,
Putting forward the proposal to backport GEODE-9091 (Serialization Improvements) to support/1.14 branch,
What does GEODE-9091 do?
* It adds serialVersionUID to the Serializable classes in geode-redis module
* It converts all DataSerializable classes to DataSerializableFixedID classes
Why do we need to backport these changes?
* These changes future-proofs the geode-redis data structures from being used in mixed version clusters.
* This will ensure that changes to serializable classes do not break backward compatibility.
* If these classes get changed in the future, the serialVersionUIDs will remain the same and can be used with older and newer versions.
* If we don't backport these changes to 1.14.0 then future releases of geode-redis will not be compatible with it.
Reference PR:[link<https://github.com/apache/geode/pull/6115>]
Regards
Nabarun Nag
Re: [Poposal] Backport GEODE-9019 to Apache Geode 1.14.0 branch
Posted by Sarah Abbey <sa...@vmware.com>.
+1
________________________________
From: Nabarun Nag <nn...@vmware.com>
Sent: Thursday, March 11, 2021 1:48 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: [Poposal] Backport GEODE-9019 to Apache Geode 1.14.0 branch
Hi everyone,
Putting forward the proposal to backport GEODE-9091 (Serialization Improvements) to support/1.14 branch,
What does GEODE-9091 do?
* It adds serialVersionUID to the Serializable classes in geode-redis module
* It converts all DataSerializable classes to DataSerializableFixedID classes
Why do we need to backport these changes?
* These changes future-proofs the geode-redis data structures from being used in mixed version clusters.
* This will ensure that changes to serializable classes do not break backward compatibility.
* If these classes get changed in the future, the serialVersionUIDs will remain the same and can be used with older and newer versions.
* If we don't backport these changes to 1.14.0 then future releases of geode-redis will not be compatible with it.
Reference PR:[link<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fpull%2F6115&data=04%7C01%7Csabbey%40vmware.com%7C60e78e0c3e754a62a2ac08d8e4be51ba%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510853355938019%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=q10KkgoD48qcccbXwaD89v7xbcZR9Q5QF0EpceXLgT8%3D&reserved=0>]
Regards
Nabarun Nag
Re: [Poposal] Backport GEODE-9019 to Apache Geode 1.14.0 branch
Posted by Owen Nichols <on...@vmware.com>.
Now is definitely the time to fix this. Glad to have this added to blocker board.
On 3/11/21, 11:09 AM, "Jens Deppe" <jd...@vmware.com> wrote:
+1
On 3/11/21, 10:49 AM, "Nabarun Nag" <nn...@vmware.com> wrote:
Hi everyone,
Putting forward the proposal to backport GEODE-9091 (Serialization Improvements) to support/1.14 branch,
What does GEODE-9091 do?
* It adds serialVersionUID to the Serializable classes in geode-redis module
* It converts all DataSerializable classes to DataSerializableFixedID classes
Why do we need to backport these changes?
* These changes future-proofs the geode-redis data structures from being used in mixed version clusters.
* This will ensure that changes to serializable classes do not break backward compatibility.
* If these classes get changed in the future, the serialVersionUIDs will remain the same and can be used with older and newer versions.
* If we don't backport these changes to 1.14.0 then future releases of geode-redis will not be compatible with it.
Reference PR:[link<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fpull%2F6115&data=04%7C01%7Conichols%40vmware.com%7Ca2d79be99dd54c16b4b708d8e4c123d6%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510865516229676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=I%2FASI9ogVDTMx%2F17agyKUVtBAtlc8L22CFegf71RQWE%3D&reserved=0>]
Regards
Nabarun Nag
Re: [Poposal] Backport GEODE-9019 to Apache Geode 1.14.0 branch
Posted by Jens Deppe <jd...@vmware.com>.
+1
On 3/11/21, 10:49 AM, "Nabarun Nag" <nn...@vmware.com> wrote:
Hi everyone,
Putting forward the proposal to backport GEODE-9091 (Serialization Improvements) to support/1.14 branch,
What does GEODE-9091 do?
* It adds serialVersionUID to the Serializable classes in geode-redis module
* It converts all DataSerializable classes to DataSerializableFixedID classes
Why do we need to backport these changes?
* These changes future-proofs the geode-redis data structures from being used in mixed version clusters.
* This will ensure that changes to serializable classes do not break backward compatibility.
* If these classes get changed in the future, the serialVersionUIDs will remain the same and can be used with older and newer versions.
* If we don't backport these changes to 1.14.0 then future releases of geode-redis will not be compatible with it.
Reference PR:[link<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fpull%2F6115&data=04%7C01%7Cjdeppe%40vmware.com%7Ca9af716b88864596194608d8e4be53d4%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C637510853397887556%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zTWX4rH7V4uEHSx63uwO3cfokQ%2FR3tU9MY3otuS9Lhc%3D&reserved=0>]
Regards
Nabarun Nag