[
https://issues.apache.org/jira/browse/IGNITE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144015#comment-15144015
]
Oddo commented on IGNITE-1144:
------------------------------
Val,
Thanks!
I have fixed most of the issues you raised in your comments. One thing I am
confused about is the Async support in the queues and sets. For example, in the
IgniteQueue.java code, I can see a comment like this one:
"* All queue operations have synchronous and asynchronous counterparts."
However, neither queue or set implementations in Ignite seem to support
asynchronous operations (unless I am looking at the wrong code/places). Hence,
I think I should remove the reference to Async support in affinityRun/Call
implementations.
Let me know what you think.
Thanks!
> 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)
