[
https://issues.apache.org/jira/browse/IGNITE-12964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111025#comment-17111025
]
Aleksey Plekhanov commented on IGNITE-12964:
--------------------------------------------
[~ptupitsyn], this ticket introduces CLUSTER_GROUP feature (not CLUSTER_API
feature). Cluster group API was implemented in 2.9 and not released.
CLUSTER_API feature was introduced by IGNITE-12407, and this feature shows that
cluster states are supported by the server. See java thin client
implementation: {{ClientClusterImpl}}, there are both features checked (version
based or bitmask based), but state ACTIVE_READ_ONLY is only possible when
bitmask feature is supported by the server. Also, there is javadoc for
{{ProtocolBitmaskFeature.CLUSTER_API}} on the client-side describing the
purpose of this feature.
> Java thin client: implement cluster group API
> ---------------------------------------------
>
> Key: IGNITE-12964
> URL: https://issues.apache.org/jira/browse/IGNITE-12964
> Project: Ignite
> Issue Type: New Feature
> Components: thin client
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Fix For: 2.9
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Implement API for node filtering on java thin client side. Thin-client API
> should match thick-client API ({{ClusterGroup}}, {{ClusterNode}} classes) as
> much as possible.
> Already implemented server-side thin-client operations
> {{OP_CLUSTER_GROUP_GET_NODE_IDS}}, {{OP_CLUSTER_GROUP_GET_NODE_INFO}} should
> be used.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
