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,
Most likely, Scala Vector can't be used as a key as-is due to it's
implementation [1].
I'm not sure, if k1 and k2 scala objects have same internal structure to
Ignite can serialize them to same binary representation.
[1]
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?
--
Hi,
Ignite doesn't rely on BinaryObject hashcode or equals method, it use
internal comparison logic instead.
So, it is ok BinaryObject.equals() return true if compared with same object
only.
As Ignite have no hooks for scala collections, they will be handled as
regular user objects.
Let us know
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:
