Re: affinityRun() and affinityCall() (JIRA ticket)

Val, Before I go on and submit pull requests etc. - would you comment on the path I am taking with this? As I said I am not a JAVA developer but I am trying to teach myself the language and contribute at the same time ;) Here are my thoughts on implementing this for the queue

Re: affinityRun() and affinityCall() (JIRA ticket)

Responded in the ticket. -Val On Fri, Jan 29, 2016 at 7:05 AM, Dood@ODDO wrote: > Val, > > Before I go on and submit pull requests etc. - would you comment on the > path I am taking with this? As I said I am not a JAVA developer but I am > trying to teach myself the

Re: affinityRun() and affinityCall() (JIRA ticket)

Hi, We should assign the ticket to you. Can you please send your Jira username here (you can create one)? This way I will add you to a list of Ignite contributors in Jira and assign the ticket to you. D. On Wed, Jan 27, 2016 at 9:13 AM, Dood@ODDO wrote: > Hello, > > I am

affinityRun() and affinityCall() (JIRA ticket)

Hello, I am playing with https://issues.apache.org/jira/browse/IGNITE-1144 as introduction to hacking on Ignite. I am not a Java developer by day but have experience writing code in various languages. This is my first in-depth exposure to Ignite internals (have lightly used it as a user in a

Re: affinityRun() and affinityCall() (JIRA ticket)

Hi, Both GridCacheQueueAdapter and GridCacheSetImpl have a reference to GridCacheContext which represents the underlying cache for the data structure. GridCacheContext.name() will give you the correct cache name that you can use when calling affinityRun method. -Val On Wed, Jan 27, 2016 at 9:13

Re: affinityRun() and affinityCall() (JIRA ticket)

On Wed, Jan 27, 2016 at 5:48 PM, Dmitriy Setrakyan wrote: > > > On Wed, Jan 27, 2016 at 4:36 PM, Dood@ODDO wrote: > >> On 1/27/2016 5:33 PM, Dmitriy Setrakyan wrote: >> >>> Hi, >>> >>> We should assign the ticket to you. Can you please send your Jira