ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Valentin Kulichenko <valentin.kuliche...@gmail.com>
Subject Re: Async and sync ops in IgniteQueue and IgniteSet implementations
Date Fri, 12 Feb 2016 19:49:49 GMT
Hi,

First of all, the JavaDoc is incorrect, there are no async counterparts for
queue and set operations in the current API.

The question is - do we need them? I think we should have have them for new
affinityRun and affinityCall methods that you're adding, but I'm not sure
about others.

Does anyone has thoughts on this?

-Val

On Fri, Feb 12, 2016 at 11:07 AM, Dood@ODDO <oddodaoddo@gmail.com> wrote:

> Hello all,
>
> This may be a very dumb question (and feel free to "reprimand" me ;-) but
> I will ask it anyways.
>
> I am working on https://issues.apache.org/jira/browse/IGNITE-1144 and one
> of the comments on the submitted code was that I marked both methods I am
> implemented as @IgniteAsyncSupported but I never actually provided an async
> implementation. All my methods do is call on methods already implemented in
> IgniteCompute.java (after verifying that the methods are called on data
> structures that are collocated) and my assumption was that the methods
> being called are already implemented in async/sync versions. Specifically,
> these methods are affinityRun() and affinityCall().
>
> Furthermore, I noticed the following comment in IgniteQueue.java, for
> example:
> ""* All queue operations have synchronous and asynchronous counterparts."".
>
> However, after looking at all the implementations of IgniteQueue interface
> in the code base, I could not find any actual implementations of
> asynchronous calls on any methods of queue or set. Am I just missing
> something really basic?
>
> Thanks!
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message