I agree that this interface is problematic. However, I don't think that dropping it right away would be fair to our users. Can we deprecate it and print out a warning that AffinityKeyMapper cannot be used with DDL statements?
D. On Tue, Apr 11, 2017 at 12:32 AM, Sergi Vladykin <[email protected]> wrote: > Guys, > > We are moving in direction of better distributed SQL support, it means that > we always will need to know an affinity field name for key type. > > Now we have AffinityKeyMapper which hides it from us. > > Since we have other means of configuring the affinity key, e.g > CacheKeyConfiguration and @AffinityKeyMapped, I suggest to either drop this > interface or change it so that it just return affinity key field name > instead of the affinity key field value. I prefer dropping it. > > What do you think? > > Sergi >
