Ignite stores data in binary form and has its own algorithms for hashCode/equals that are based on binary representation to avoid deserialization. Therefore overriding equals would not have any affect.
Actually, I'm not sure I understand why you want to override it in the first place. The following example is confusing: > For eg: A custom key has an equals method that checks for a field to be > equal to 0 and for another key has an equals method that checks for a > field > to be equal to 1. You should compare two different objects for equality rather than comparing different objects' fields with particular values. Can you clarify this? -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
