Vladimir,
Thanks for the clarification.
Igor
On Jun 20, 2017 2:37 AM, "Vladimir Ozerov" wrote:
> Igor,
>
> This exception is just a regression from recent work on binary
> serialization in the scope of 2.0 release. If BinaryMarshaller is set, we
> should not force users to have equals/hashCode
Igor,
This exception is just a regression from recent work on binary
serialization in the scope of 2.0 release. If BinaryMarshaller is set, we
should not force users to have equals/hashCode methods on keys. There is a
ticket [1], hopefully it will be merged to master soon.
Vladimir.
[1] https://
If the server doesn't calculate hash code how it then should work for
objects which expired from cache and were pushed to persistent store?
As far as persistent store methods (loadCache, load, loadAll) will be
executed on server side it looks like server should have custom logic for
hashCode() and
Igor,
As far as I know, the hash code would be calculated on the client side and
sent over within the binary format. Server does not calculate the hash code.
D.
On Tue, Jun 20, 2017 at 12:08 AM, Igor Rudyak wrote:
> Hi,
>
> I am using simple POJO objects as key/value pair for my Ignite cache.
Hi,
I am using simple POJO objects as key/value pair for my Ignite cache. Also
I would like to store objects as BinaryObjects. Thus Ignite cache was
created using:
*mycache = ignite.getOrCreateCache("mycache").withKeepBinary()*
When I am trying to put objects in the cache I am receiving such an
