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

2018-09-23 Thread kcheng.mvp
Thank you very much! -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

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

2018-09-19 Thread Ilya Kasnacheev
Hello! Why don't you use CacheKeyConfiguration as mentioned in the ticket? Regards, -- Ilya Kasnacheev ср, 19 сент. 2018 г. в 5:55, 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

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

2018-09-18 Thread 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/

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

2018-09-18 Thread 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 *Aff