I've posted proposed example of hash code resolver interface and XML configuration for classless key on issue page https://issues.apache.org/jira/browse/IGNITE-2294.
2016-09-29 20:16 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > On Thu, Sep 29, 2016 at 9:57 AM, Denis Magda <dma...@gridgain.com> wrote: > >> Alex, >> >> A minor note regarding this >> >> > On Sep 29, 2016, at 8:39 AM, Alexey Goncharuk < >> alexey.goncha...@gmail.com> wrote: >> > >> > A set of fields participating in hashCode and equals is impossible to >> > change without cluster restart. >> >> It’s unlikely that someone will change a key or at least it should be a >> rare or accidental operation. In any case if this happens a user must >> upgrade all the keys he already has in a cache. To resolve this it’s >> simpler to create a new cache with updated configuration and populate data >> there. This will not require us to restart a cluster. >> > > We should have a check in code that would prohibit changing hashcode fields > or the hashcode resolver class within the same cache. Using a different > cache to store the keys with new hashcodes is always an option and does not > require anything special from our side. > > >> >> — >> Denis
