Ok, I tried to write generic impl to use the same key class with different caches . That's why kept the name affinityId. The reason I am not getting error is I have the subscriptionId in Data(value) class as well.
So it means the affinity key field name matters. I was thinking/trying to map the affinity column name "subscriptionId" to field "affinityId" without keeping the field name same. Was looking in wrong direction. Thanks, Prasad Thanks, Prasad On Wed, Aug 22, 2018, 9:29 PM vkulichenko <[email protected]> wrote: > Prasad, > > In this case using subscriptionId in query would be a syntax error, because > the name of the field is affinityId. If you use affinityId, however, Ignite > will route the query to a single node. It knows that it's affinity key > based > on @AffinityKeyMapped annotation. > > -Val > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > On Wed, Aug 22, 2018, 9:29 PM vkulichenko <[email protected]> wrote: > Prasad, > > In this case using subscriptionId in query would be a syntax error, because > the name of the field is affinityId. If you use affinityId, however, Ignite > will route the query to a single node. It knows that it's affinity key > based > on @AffinityKeyMapped annotation. > > -Val > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
