Awesome, that's super clear!
One last question, will full_async have better performance over the other
two usually?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Andrew,
Thanks a lot for the response!
While reproducing the case, I found that: If I set
CacheWriteSynchronizatoinMode to FULL_ASYNC, EntryProcessorException is
ignored. But if I set it PRIMARY_SYNC, then the EntryProcessorException will
be thrown.
Is it intentional that under FULL_ASYNC
Yeah, I believe k1 and k2's internal structure are different, and therefore
causing the problem
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Developers,
I am not sure if I understand the IgniteCache invoke method API correctly
here:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html#invoke-K-org.apache.ignite.cache.CacheEntryProcessor-java.lang.Object...-
Got it. I thought IgniteCache converts key to BinaryObject and then compares
them, and therefore gave the example.
However, if I put key k1 with a value into IgniteCache, and retrieve the
value using k2, I won't be able to find the entry. Do you know what's the
process behind this process?
--
Thanks a lot for the wonderful development on Ignite. I am wondering if there
is any plan to support Scala Collection (e.g. Vector) as key?
There is support for common Java Collection, see here:
