ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: AffinityKeyMapper alternatives
Date Tue, 12 Sep 2017 01:24:54 GMT
On Mon, Sep 11, 2017 at 4:47 PM, Valentin Kulichenko <
valentin.kulichenko@gmail.com> wrote:

> Even if CacheKeyConfiguration is part of CacheConfiguration, the affinity
> key field name can be provided only on cache startup. In many cases this
> name can be resolved only based on the actual key instance, e.g. during
> first put. Per my understanding, this already works with annotation, I just
> propose more flexible solution for rare cases when annotation can't be
> used. Basically, the logic we currently have would become the default
> implementation of the resolver.

Val, the use case seems very strange to me. How can you not know the
affinity key field in advance? Can you provide an example from the field?

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