ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@gridgain.com>
Subject Re: Default hash code generation strategy for new binary objects
Date Thu, 29 Sep 2016 16:57:06 GMT

A minor note regarding this

> On Sep 29, 2016, at 8:39 AM, Alexey Goncharuk <alexey.goncharuk@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.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message