Andrey Gura created IGNITE-2646:
---
Summary: IgniteCompute.withAsync can execute tasks synchronously
Key: IGNITE-2646
URL: https://issues.apache.org/jira/browse/IGNITE-2646
Project: Ignite
Issue
I've created ticket https://issues.apache.org/jira/browse/IGNITE-2646
On Thu, Feb 11, 2016 at 4:12 PM, Andrey Gura wrote:
> Dmitry,
>
> GridTaskProcessor does't know what kind of IgniteCompute implementation
> was used by client code. So we need some kind of flag that will
Guys,
during debugging of failed test
(GridSessionCheckpointSelfTest.testSharedFsCheckpoint) I've noticed that
GridTaskWorker can invoke reduce() method in caller thread.
If task isn't annotated by @ComputeTaskMapAsync then mapping job will be
run in caller thread. Since job mapping will be
Andrey,
I think we should keep it simple. From the API standpoint, I am not sure
why not just always execute the task asynchronously every time when
withAsync() API is invoked? Why add additional parameters to the API?
D.
On Wed, Feb 10, 2016 at 6:53 AM, Andrey Gura wrote: