[
https://issues.apache.org/jira/browse/IGNITE-8936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644832#comment-16644832
]
ASF GitHub Bot commented on IGNITE-8936:
----------------------------------------
GitHub user vsisko opened a pull request:
https://github.com/apache/ignite/pull/4942
IGNITE-8936 Fixed Java version check.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9836
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4942.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4942
----
commit 5b8d5901ad20319f1c3181995bb8c3d6a4e8d9e5
Author: vsisko <vsisko@...>
Date: 2018-10-10T10:16:35Z
IGNITE-8936 Fixed Java version check.
----
> 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
> Fix For: 2.7
>
> 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)
