You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2024/06/19 09:23:00 UTC
[jira] [Updated] (IGNITE-22435) Add JobTarget interface to Compute API
[ https://issues.apache.org/jira/browse/IGNITE-22435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-22435:
------------------------------------
Summary: Add JobTarget interface to Compute API (was: Add ExecutionTarget interface to Compute API)
> Add JobTarget interface to Compute API
> --------------------------------------
>
> Key: IGNITE-22435
> URL: https://issues.apache.org/jira/browse/IGNITE-22435
> Project: Ignite
> Issue Type: Improvement
> Components: compute
> Affects Versions: 3.0.0-beta1
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Currently, there are too many methods in Compute API. This comes from the need to pick target nodes in different ways:
> * Any one node (don't care which one, just run my job)
> * Specific node by name
> * Specific node by key (colocated)
> * All nodes (broadcast)
> A cleaner approach would be to introduce *ExecutionTarget* interface with corresponding factory methods:
> * *any*
> * *all*
> * *fromNodeName*
> * *fromColocationKey*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)