Hello!
You can try specifying BinaryConfiguration where you would supply a
BinaryTypeConfiguration for this type name, specifying a custom
BinarySerializer. Then you can try supplying BinaryReflectiveSerializer
there.
See
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configu
no, because we use third party classes and cannot change them
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
If I delete only methods (leave the interface), then there are no errors.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
Does it solve your issue?
Regards,
--
Ilya Kasnacheev
ср, 2 дек. 2020 г. в 16:50, Surkov.Aleksandr :
> If I delete only methods (leave the interface), then there are no errors.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Hi igniters!
We use third party classes and store them objects in key-value cache.
This class implements the Serializable interface and defines the readObject
and writeObject methods.
After we decided to switch to a new version of the class and tried to read
from the cache, we received an error:
Hello!
Does this still happen if you get rid of Serializable, readObject,
writeObject?
Regards,
--
Ilya Kasnacheev
ср, 2 дек. 2020 г. в 09:58, Surkov.Aleksandr :
> Hi igniters!
>
> We use third party classes and store them objects in key-value cache.
> This class implements the Serializable i
