You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Eduard Shangareev (JIRA)" <ji...@apache.org> on 2018/05/31 16:03:00 UTC

[jira] [Assigned] (IGNITE-8673) Reconcile isClient* methods

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

Eduard Shangareev reassigned IGNITE-8673:
-----------------------------------------

    Assignee: Eduard Shangareev

> Reconcile isClient* methods
> ---------------------------
>
>                 Key: IGNITE-8673
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8673
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Eduard Shangareev
>            Assignee: Eduard Shangareev
>            Priority: Critical
>             Fix For: 2.6
>
>
> Now isClient (Mode, Cache and so on) method semantic could mean different things:
> -the same as IgniteConfiguration#setClientMode;
> -or the way how a node is connected to cluster (in the ring or not).
> Almost in all cases, we need the first thing, but actually methods could return second.
> For example, ClusterNode.isClient means second, but all of us use as first.
> So, I propose to make all methods return first.
> And if there are places which require second replace them with the usage of forceClientMode.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)