Andrey,
This ticket seems to be about the same issue:
https://issues.apache.org/jira/browse/IGNITE-6944
Can you please take a look and provide your thoughts?
-Val
On Tue, Nov 7, 2017 at 4:02 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> *cross-posting to dev*
>
> Hi Chris,
Thanks Val.
BTW: It would be pretty easy to write a unit test for this.
1) Create an Instance (A) of a class that contains an ImmutableList
foo;
2) Create a cache of these
3) Using the BinaryMarshaler -- put(A), then get(A)
4) Walk the items in foo. (I will not blow up unless you access elements o
*cross-posting to dev*
Hi Chris,
This is a regression due to this fix:
https://issues.apache.org/jira/browse/IGNITE-6485. For some reason, since
2.3 it is looking for readResolve/writeReplace methods only in exact class
that is being serialized, but not in the whole hierarchy.
*Andrey G*, since
Hi Val
I have found that if I switch from
igniteConfig.setMarshaller(new BinaryMarshaller());
To:
igniteConfig.setMarshaller(new
OptimizedMarshaller().setRequireSerializable(false));
Then everything works again.
Although I am worried that this will have a terrible effect on performan
guava 21.0
Thanks,
-- Chris
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Chris,
Which version of Guava are you using?
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
I tried upgrading to Ignite 2.3.0, and now one of my unit tests is failing
(the ONLY change was an upgrade from 2.2.0-> 2.3.0)
The Unit Test in question is the simplest “put, then get” test – to validate
proper round-tripping of cache data.
In other words, what is going in is not equal to w
