Each compute method produces task. For 'run', 'call' etc. methods the
classes of tasks are internal.
There are tests checking the task session by ComputeTaskFuture for these
methods.
I think we have to leave real class of future is
ComputeTaskInternalFuture#ComputeFuture to compatibility.
The class of the future at the public API may be changed.
On 20.01.2017 17:54, Vladimir Ozerov wrote:
IgniteCompute was designed this way initially. See IgniteCompute.future()
override. May be it makes sense to leave this type only for execute(...)
methods.
On Fri, Jan 20, 2017 at 5:45 PM, Semyon Boikov <sboi...@gridgain.com> wrote:
Hi Taras,
Why 'async' methods return ComputeTaskFuture, not just IgniteFuture? It
seems that ComputeTaskFuture is needed only for tasks?
On Fri, Jan 20, 2017 at 5:18 PM, Taras Ledkov <tled...@gridgain.com>
wrote:
Gents
I've done changes of the IgniteCompute as a subtask of the whole async
API
refactoring (https://issues.apache.org/jira/browse/IGNITE-4580).
Please check the new version of the public API (
https://github.com/gridgain/apache-ignite/blob/b81621bf2e8a
35b20989f95ff52c0f6d91dd75d6/modules/core/src/main/java/
org/apache/ignite/IgniteCompute.java)
Please look through the new API and let me know any comments.
--
Taras Ledkov
Mail-To: tled...@gridgain.com
--
Taras Ledkov
Mail-To: tled...@gridgain.com
