From 4689be8f36a8c0b5c339d3b1095dcc02f4e8ddee Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Krzysztof=20Jamr=C3=B3z?= <79092062+k-jamroz@users.noreply.github.com> Date: Wed, 4 Feb 2026 17:15:57 +0100 Subject: [PATCH] Remove mentions of 5.2 in Compact serialization docs Removed notes regarding the promotion of Compact serialization to stable status and compatibility issues with previous BETA versions. --- .../pages/compact-serialization.adoc | 22 ------------------- 1 file changed, 22 deletions(-) diff --git a/docs/modules/serialization/pages/compact-serialization.adoc b/docs/modules/serialization/pages/compact-serialization.adoc index bbe5f3768..e5365e259 100644 --- a/docs/modules/serialization/pages/compact-serialization.adoc +++ b/docs/modules/serialization/pages/compact-serialization.adoc @@ -39,11 +39,6 @@ Java classes and records, and .NET classes which are cached and reused later, wi The underlying format of the Compact serialized objects is platform and language independent. -NOTE: Compact serialization is promoted to the stable status in the 5.2 Hazelcast release. -The older versions released under the BETA status are not compatible with the stable 5.2 version. + -For future versions, the backward compatibility will be maintained, just like any other -Hazelcast feature. - == Configuration The configuration can be used to register either @@ -1625,27 +1620,10 @@ xref:sql:mapping-to-maps.adoc#compact-objects[Compact Object mappings] section t Hazelcast supports WAN replication of the Compact serialized objects between different clusters. -However, since the Compact serialization is promoted to the stable status in 5.2, and it is not -compatible with the previous BETA versions, one has to make sure that the whole WAN cluster -topology members, including all senders and receivers, are at least as new as 5.2, before starting to -replicate data structures containing Compact serialized objects. - -Since the Compact serialization has promoted to the stable status, it will be possible to -replicate Compact serialized objects between different WAN clusters in the future releases. - == Persistence Support Hazelcast supports persisting Compact serialized objects and reading the persisted data on startup. -However, since the Compact serialization is promoted to the stable status in 5.2, and it is not -compatible with the previous BETA versions, it is not possible to recover the Hazelcast members -with the persisted data of Compact serialized objects of the previous Hazelcast versions, where -this feature was in BETA. - -Since it has promoted to the stable status, it will be possible in the future releases to -persist and recover Compact-serialized objects of different Hazelcast versions, at least as -new as 5.2. - == Serialization Priority Compact serialization has the highest xref:serialization:serialization.adoc#steps[priority] of