About work around for https://issues.apache.org/jira/browse/IGNITE-5795

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

About work around for https://issues.apache.org/jira/browse/IGNITE-5795

kcheng.mvp
I ran into the same issue as
http://apache-ignite-users.70518.x6.nabble.com/SQL-SELECT-with-AffinityKeyMapped-no-results-td23141.html#a24232


from the document https://apacheignite.readme.io/docs/affinity-collocation,
there are two ways to achieve *Affinity*.  I would like to confirm that use
*AffinityKey* has the same issue or not?


Thanks.



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: About work around for https://issues.apache.org/jira/browse/IGNITE-5795

kcheng.mvp
I checked the source code just now and found *AffinityKey* is using
*@AffinityKeyMapped*
that's to  say *AffinityKey* has the same issue.
am I right?



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: About work around for https://issues.apache.org/jira/browse/IGNITE-5795

Ilya Kasnacheev
Hello!

Why don't you use CacheKeyConfiguration as mentioned in the ticket?

Regards,
--
Ilya Kasnacheev


ср, 19 сент. 2018 г. в 5:55, kcheng.mvp <[hidden email]>:

> I checked the source code just now and found *AffinityKey* is using
> *@AffinityKeyMapped*
> that's to  say *AffinityKey* has the same issue.
> am I right?
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
Reply | Threaded
Open this post in threaded view
|

Re: About work around for https://issues.apache.org/jira/browse/IGNITE-5795

kcheng.mvp
Thank you very much!



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/