You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikolai Kulagin (JIRA)" <ji...@apache.org> on 2018/08/27 08:24:00 UTC
[jira] [Commented] (IGNITE-8936) Remove
AffinityAssignment#clientEventChange as not used
[ https://issues.apache.org/jira/browse/IGNITE-8936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593304#comment-16593304 ]
Nikolai Kulagin commented on IGNITE-8936:
-----------------------------------------
Remove field clientEvtChange and method clientEventChange()
PR: [https://github.com/apache/ignite/pull/4448|https://github.com/apache/ignite/pull/4448]
TC: [https://ci.ignite.apache.org/viewLog.html?buildId=1723097&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll&logTab=]
Project is buildable, tests are ok, flacky as usual. [~Mmuzaf], please, review my change.
> Remove AffinityAssignment#clientEventChange as not used
> -------------------------------------------------------
>
> Key: IGNITE-8936
> URL: https://issues.apache.org/jira/browse/IGNITE-8936
> Project: Ignite
> Issue Type: Task
> Affects Versions: 2.7
> Reporter: Maxim Muzafarov
> Assignee: Nikolai Kulagin
> Priority: Minor
> Labels: newbie
> Attachments: ClientEventChange (1).png
>
>
> We should try to keep Ignite project code as simple as possible.
> Motivation: http://apache-ignite-developers.2346864.n4.nabble.com/Cases-of-using-AffinityAssignment-clientEventChange-method-td32068.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)