You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2020/05/19 08:49:00 UTC
[jira] [Comment Edited] (IGNITE-12964) Java thin client: implement
cluster group API
[ https://issues.apache.org/jira/browse/IGNITE-12964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110972#comment-17110972 ]
Aleksey Plekhanov edited comment on IGNITE-12964 at 5/19/20, 8:48 AM:
----------------------------------------------------------------------
[~ptupitsyn] when cluster group API was added by IGNITE-12385 no feature flag was introduced (and no version increment was made), there is no way from client-side to check if the server supports cluster group API. There was no release since IGNITE-12385 so it's safe to fix this problem.
was (Author: alex_pl):
[~ptupitsyn] when cluster group API was added by IGNITE-12385 no feature flag was introduced (and no version increment), there is no way from client-side to check if the server supports cluster group API. There was no release since IGNITE-12385 so it's safe to fix this problem.
> 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)