[
https://issues.apache.org/jira/browse/IGNITE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132437#comment-15132437
]
ASF GitHub Bot commented on IGNITE-1144:
----------------------------------------
GitHub user oddodaoddo opened a pull request:
https://github.com/apache/ignite/pull/459
IGNITE-1144 Add affinity functions to collocated Ignite Queue and Set
Properly branched pull request as per instructions here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/oddodaoddo/ignite IGNITE-1144
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/459.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #459
----
commit 81ec8cb5cc5acf9f87893abe1d81a4d0260b8de6
Author: Oddo Da <[email protected]>
Date: 2016-02-04T15:20:39Z
IGNITE-1144 Add affinity functions to collocated Ignite Queue and Set
----
> 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)
