From c1d0a1132739d42f40b799e8fd255e0061fe4cb7 Mon Sep 17 00:00:00 2001 From: Shawn Date: Sun, 8 Oct 2023 01:06:34 +0800 Subject: [PATCH] Update java_object_graph_guide.md (#987) --- docs/guide/java_object_graph_guide.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/guide/java_object_graph_guide.md b/docs/guide/java_object_graph_guide.md index 10b7279083..05e15931e9 100644 --- a/docs/guide/java_object_graph_guide.md +++ b/docs/guide/java_object_graph_guide.md @@ -345,8 +345,12 @@ if(JavaSerializer.serializedByJDK(bytes)){ ### Upgrade fury Currently binary compatibility is ensured for minor versions only. For example, if you are using fury`v0.2.0`, binary compatibility will -be provided if you upgrade to fury `v0.2.1`. But if upgrade to fury `v0.3.0`, no binary compatibility are ensured. In order to not -break binary compatibility, you need to write fury version as header to serialized data using following code: +be provided if you upgrade to fury `v0.2.1`. But if upgrade to fury `v0.3.0`, no binary compatibility are ensured. +Most of the time there is no need to upgrade fury to newer major version, the current version is fast and compact enough, +and we provide some minor fix for recent older versions. + +But if you do want to upgrade fury for better performance and smaller size, you need to write fury version as header to serialized data +using code like following to keep binary compatibility: ```java MemoryBuffer buffer = xxx; buffer.writeVarInt(2);