Got it, thanks for the info.
Thanks,
Calvin
-Original Message-
From: dkarachentsev [mailto:dkarachent...@gridgain.com]
Sent: Monday, July 16, 2018 9:57 PM
To: user@ignite.apache.org
Subject: RE: Best practice for class versioning: marshaller error
Hi Calvin,
> Can I ass
Hi Calvin,
> Can I assume that BinaryMarshaller won't be used for any object embedded
> inside GridCacheQueryResponse?
Yes, because Binary can fallback to Optimized, but not vice versa.
> If I am correct, do you have any suggestion on how I can avoid this type
> of issue?
Probably you need
ignite-core-2.3.0-clsa.20180130.59.jar:2.3.0-clsa.20180130.59]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1526)
~[ignite-core-2.3.0-clsa.20180130.59.jar:2.3.0-clsa.20180130.59]
<<<<<<<<<<<<<<&
Hello,
In that case, only 'createdTime' fall back to OptimizedMarshaller.
Thanks,
Slava.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
k to OptimizedMarshaller.
-Calvin
-Original Message-
From: dkarachentsev [mailto:dkarachent...@gridgain.com]
Sent: Thursday, June 28, 2018 2:59 PM
To: user@ignite.apache.org
Subject: RE: Best practice for class versioning: marshaller error
Hi Calvin,
1. Enlist I mean that if you want, fo
Hi Calvin,
1. Enlist I mean that if you want, for example, to get to see what fields
present in BinaryObject. In other words, if you want to work with
BinaryObject directly. For POJO serialization/deserialization this should
not be and issue at all.
2-3. In your case, you have and java.time.Ser
-
From: dkarachentsev [mailto:dkarachent...@gridgain.com]
Sent: Wednesday, June 27, 2018 8:52 PM
To: user@ignite.apache.org
Subject: Re: Best practice for class versioning: marshaller error
Hi Calvin,
BinaryMarshaller can solve that issue with involving a few more.
First of all, you will need to d
Hi Calvin,
BinaryMarshaller can solve that issue with involving a few more.
First of all, you will need to disable compact footer to let each
BinaryObject has it's schema in footer.
If you need just put/get POJOs everything will be fine. But you need to
enlist your POJO in BinaryConfiguration
Hi,
I am running Ignite 2.3 using Cassandra as my persistence store.
I got unmarshall error when a server node trying to unmarshall an object of old
version from Cassandra.
This is the scenario:
1. Object of ClassA (older version) is serialized and persisted into
Cassandra
2.
