[
https://issues.apache.org/jira/browse/IGNITE-21270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809314#comment-17809314
]
Pavel Tupitsyn commented on IGNITE-21270:
-----------------------------------------
I don't think that stringly-typed API is better. We should definitely keep
*ClusterNode* in the public API, it can't be replaced with a string:
* To access address and metadata
* Future-proofing
> 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 API capabilities (we'll just resolve the nodes internally in the
> very beginning), 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)
