kryo

kryo copied to clipboard

[POC] FieldSerializer for Records

1

This is a POC for moving record serialization from `RecordSerializer` into `FieldSerializer`. This approach has two main advantages: 1. Existing configuration options for the `FieldSerializer` can be used for records...

theigl

GraalVM compatibility

13

**Is your feature request related to a problem? Please describe.** Make Kryo lib GraalVM compatible **Describe the solution you'd like** Some of serializers can't be used in GraalVM - https://github.com/redisson/redisson/issues/4811....

mrniko

CachedFields are not reset when references-flag changes

3

**Describe the bug** When changing the `references` flag from false to true on a kryo instance that has already been used for deserializing, subsequent deserialization does not work correctly any...

thomas-z96

Add a hook to intercept registration of all new serializers.

11

Create a mechanism for customising, configuring, or even replacing a serializer when it is registered. See #943.

chrisr3

Allow turning a few optimisations off for Kryo 5.4.0

20

We are upgrading our code-base from Kryo 4.0.2 to 5.4.0, and have hit an issue when serialising a `Collection` that only contains instances of `Collections$UnmodifiableRandomAccessList`. We have sub-classed `Kryo` to...

chrisr3

Urgent: Data Corruption Issue Identified During DTO Deserialization (Instance Variable Renamed/Type Changed)

10

**Describe the bug** We've identified data corruption during DTO deserialization when there are changes in existing fields/instance variables in a dto **To Reproduce** Have a simple dto, lets say employee...

geekthread

schema validation failed while deserialize data serialized by Encoder.Bean Serializer using Kryo.

1

**Describe the bug** For stateful spark structured Streaming query processing, Used RocksDB state store, and existing state data is serialized by Spark's Encoders.bean serializer, still to have backward compatibility I...

ams45

Comparison with ObjectInputStream and ObjectOutputStream

1

Since ` ObjectInputStream`  and `ObjectOutputStream` are both part of the JDK, I consider them like the default implementation we can use to perform Object (de)serialization. I would therefore expect in...

joel-schaal

The Input class changes its buffer when deserialize a string

2

**Describe the bug** kryo 4... When I use a single byte[] array to deserialize from multiple streams, sometimes there is a crash with the error > com.esotericsoftware.kryo.kryo5.io.KryoBufferUnderflowException: Buffer underflow This...

NPE0

Kryo5 deserialization lost Locale script field

1

**Describe the bug** **java.util.Locale** **script** field in the is missing after deserialization with Kryo5, when we execute below UT method. we expect to get **sr_RS_#Cyrl** but actually we get the...

hanbing204