[
https://issues.apache.org/jira/browse/IGNITE-12964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111034#comment-17111034
]
Pavel Tupitsyn edited comment on IGNITE-12964 at 5/19/20, 10:01 AM:
--------------------------------------------------------------------
[~alex_pl] thanks for the explanation. ACTIVE_READ_ONLY addition is super
confusing. I'll update the comment on ClientBitmaskFeature - that javadoc from
ProtocolBitmaskFeature should be added to the server side as well.
Let's be more careful with flag naming and documentation. Java client is not
the only client we have.
was (Author: ptupitsyn):
[~alex_pl] thanks for the explanation. ACTIVE_READ_ONLY addition is super
confusing. I'll update the comment on ClientBitmaskFeature - that javadoc from
ProtocolBitmaskFeature should be added to the server side as well.
> 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)
