[ https://issues.apache.org/jira/browse/IGNITE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124714#comment-15124714 ]
Valentin Kulichenko commented on IGNITE-1144: --------------------------------------------- I think you're going the right way, so go ahead, create tests to check that it works and submit a pull request. Someone in community will review. The only thing: you don't need to do try-catch to just rethrow the exception. This is done automatically. > Need to have a capability to run a closure collocated with a queue/set > ---------------------------------------------------------------------- > > Key: IGNITE-1144 > URL: https://issues.apache.org/jira/browse/IGNITE-1144 > Project: Ignite > Issue Type: Improvement > Components: cache > Affects Versions: 1.1.4 > Reporter: Valentin Kulichenko > Assignee: Oddo > Priority: Critical > > Currently there is no way to do this since all collocated queues and sets are > stored in special system cache. This makes {{affinityRun()}} and > {{affinityCall()}} methods useless because it requires to explicitly provide > cache name which user doesn't know in this case. > I suggest to add {{affinityRun()}} and {{affinityCall()}} methods on > {{IgniteQueue}} and {{IgniteSet}}. They will: > * take only closure as a parameter > * throw exception for non-collocated mode > * properly delegate to sibling methods in {{Ignite}} with proper cache name > Alternatively we can add these methods on {{Ignite}} interface, which is more > consistent with the current API. But I'm not sure how to call them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)