On 3/9/2016 7:46 PM, Alexey Goncharuk wrote:
Note that withKeepBinary() is just a way to tell a cache not to deserialize
values when doing a get or running an entry processor. The concept of
binary object does not belong solely to caches - you can get an instance of
IgniteBinary interface from
Note that withKeepBinary() is just a way to tell a cache not to deserialize
values when doing a get or running an entry processor. The concept of
binary object does not belong solely to caches - you can get an instance of
IgniteBinary interface from Ignite and use binary objects in computations,
On 3/9/2016 6:43 PM, Alexey Goncharuk wrote:
Hi,
The current version of test is not very clean and it works only because
withKeepBinary() is a noop. The correct version would be to use plain cache
for non-binary-object entry processor and use withKeepBinary for
binary-object entry processor.
Hi,
The current version of test is not very clean and it works only because
withKeepBinary() is a noop. The correct version would be to use plain cache
for non-binary-object entry processor and use withKeepBinary for
binary-object entry processor. You can see that EntryProcessor creation is
Hello all,
I am working on IGNITE-2693 with Vlad Ozerov's help. I am somewhat of a
Java newbie so please be gentle ;-)
I am curious about something - after reading the Javadocs and Binary
Marshaller docs on Ignite's documentation websites, I think that the
documentation is not very friendly
