You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2024/01/16 09:47:00 UTC

[jira] [Updated] (IGNITE-21270) Use consistentId instead of ClusterNode in Compute API

     [ https://issues.apache.org/jira/browse/IGNITE-21270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Puchkovskiy updated IGNITE-21270:
---------------------------------------
    Description: 
Currently, methods of the Compute API accept ClusterNode type to identify nodes on which a job is to be executed. This seems redundant as we only use consistentId from those objects.

If we replace ClusterNode with String (representing consistentId), we will not lose expressivity, but we'll be able to move ClusterNode and TopologyService from our public API, and having less public API seems to be a good thing.

> Use consistentId instead of ClusterNode in Compute API
> ------------------------------------------------------
>
>                 Key: IGNITE-21270
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21270
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> Currently, methods of the Compute API accept ClusterNode type to identify nodes on which a job is to be executed. This seems redundant as we only use consistentId from those objects.
> If we replace ClusterNode with String (representing consistentId), we will not lose expressivity, but we'll be able to move ClusterNode and TopologyService from our public API, and having less public API seems to be a good thing.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)