Comments (3)
commented on August 19, 2024
From [email protected] on March 25, 2010 21:12:05
A first draft for this issue is checked in, r85. The class is currently named
CompatibleFieldSerializer. It supports adding and/or removing fields, which does not
invalidate previously serialized bytes. Note that it does not support changing the
type of a field.
The overhead compared to FieldSerializer is the header that is output the first time
an object of the type is serialized. The header consists of an int for the number of
fields, then a String for each field name. Also, in order to support skipping the
bytes for a field that no longer exists, for each field value I had to write an int
that is the length of the value in bytes.
from kryo.
commented on August 19, 2024
From [email protected] on April 12, 2010 14:45:54
We've got tests and everything. Calling it good for now.
Status: Fixed
from kryo.
commented on August 19, 2024
From [email protected] on October 26, 2011 22:22:15
Hi, any examples how to use this ?
from kryo.
Related Issues (20)
- Could not serialize Lambda. If anyone knows this, then please response. HOT 6
- Compatibility issue between 5.5.0 and 5.6.0 HOT 2
- failed to lazily initialize a collection, no session or session was closed while trying to deserialize SPRING_SECURITY_CONTEXT HOT 3
- Add GregorianCalendar default serializer HOT 1
- Maven artifact not found HOT 4
- Encountered ArrayIndexOutOfBoundsException when running in Apache Spark 3.3.1 HOT 3
- Allow Kryo instances to be compared using .equals() & .hashcode() HOT 3
- deserialize failure in JDK 21 HOT 5
- When an anonymous inner class is used to initialize a collection, the elements are doubled. HOT 1
- Kryo5 deserialization lost Locale script field HOT 1
- The Input class changes its buffer when deserialize a string HOT 3
- About how to build serializer by custom self-reference class HOT 4
- Cannot run benchmarks HOT 4
- Urgent: Data Corruption Issue Identified During DTO Deserialization (Instance Variable Renamed/Type Changed) HOT 10
- schema validation failed while deserialize data serialized by Encoder.Bean Serializer using Kryo. HOT 2
- Comparison with ObjectInputStream and ObjectOutputStream HOT 2
- How to configure CompatibleFieldSerializer in Kryo3 ? HOT 2
- ExternalizableSerializer does not support circular references HOT 2
- When entity add a field extends Collection, CompatibleFieldSerializer lost compatibility. HOT 4
- Invalid JDK version in profile 'jdk11ge': Unbounded range: [11, for project com.esotericsoftware:kryo-parent HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kryo.