Valya,
This future contains task session. We intentionally changed return type to
plain IgniteFuture for closure methods, as there is no notion of "session"
and "task" for them. ComputeTaskFuture now returned only from task-related
methods ("execute"). Unless I am missing something, this approach looks
correct.
On Tue, May 30, 2017 at 11:06 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Folks,
>
> I noticed that the new async API for IgniteCompute returns IgniteFuture,
> while previously we used to have its extension - ComputeTaskFuture, which
> contains useful information about the executed task session.
>
> Should this be fixed?
>
> -Val
>
