[
https://issues.apache.org/jira/browse/IGNITE-10523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708861#comment-16708861
]
ASF GitHub Bot commented on IGNITE-10523:
-----------------------------------------
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/5570
IGNITE-10523 Ignite Compatibility: add check that started node is of
expected version
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-10523
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5570.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 #5570
----
commit 7232a8f1cbfb5084cc6439b91122330fd84ce083
Author: Vyacheslav Daradur <daradurvs@...>
Date: 2018-12-04T15:20:28Z
Added check of started version
----
> Ignite Compatibility: add check that started node is of expected version
> ------------------------------------------------------------------------
>
> Key: IGNITE-10523
> URL: https://issues.apache.org/jira/browse/IGNITE-10523
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vyacheslav Daradur
> Assignee: Vyacheslav Daradur
> Priority: Major
> Fix For: 2.8
>
>
> It's necessary to check that node started in separate JVM is of a specified
> version to avoid unexpected behavior.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
