Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update java_object_graph_guide.md #987

Merged
merged 1 commit into from
Oct 7, 2023
Merged

Update java_object_graph_guide.md #987

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/guide/java_object_graph_guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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);
Expand Down