[
https://issues.apache.org/jira/browse/IGNITE-21390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-21390:
------------------------------------
Description:
*IgniteCompute.executeAsync* accepts a set of nodes. If we pass a single node
that does not exist in the cluster, the API behavior is confusing and
inconsistent across embedded and thin client modes:
{code:java}
var fakeNode = new ClusterNodeImpl("fakeId", "fakeName", new
NetworkAddress("localhost", 12345));
JobExecution<String> execution =
ignite.compute().executeAsync(Set.of(fakeNode), units(), "job", null);
execution.resultAsync().join();
{code}
was:*IgniteCompute.executeAsync* accepts a set of nodes. If we pass a single
node that does not exist in the cluster (e.g. {{new ClusterNodeImpl("fakeId",
"fakeName", new NetworkAddress("localhost", 12345))}}):
> Inconsistent behavior of Compute APIs when target node does not exist
> ---------------------------------------------------------------------
>
> Key: IGNITE-21390
> URL: https://issues.apache.org/jira/browse/IGNITE-21390
> Project: Ignite
> Issue Type: Bug
> Components: compute, thin client
> Affects Versions: 3.0.0-beta1
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> *IgniteCompute.executeAsync* accepts a set of nodes. If we pass a single node
> that does not exist in the cluster, the API behavior is confusing and
> inconsistent across embedded and thin client modes:
> {code:java}
> var fakeNode = new ClusterNodeImpl("fakeId", "fakeName", new
> NetworkAddress("localhost", 12345));
> JobExecution<String> execution =
> ignite.compute().executeAsync(Set.of(fakeNode), units(), "job", null);
> execution.resultAsync().join();
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
