[jira] [Commented] (IGNITE-8427) Apache ignite unable to connect to a minor upgrade version

["Pavel Pereslegin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-8427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619358#comment-16619358 ] 

Pavel Pereslegin commented on IGNITE-8427:
------------------------------------------

Hello [~Kinny],

According to recent [devlist discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Minor-version-changes-and-server-client-compatibility-tp34757p34905.html]:

{quote}
Ignite should be maintains (according to review checklist [1]):

- binary compatibility for persistence store between minor releases;
- JDBC and ODBC and thin client protocol forward and backward compatibility  between two consecutive minor releases;

[1] https://cwiki.apache.org/confluence/display/IGNITE/Review+Checklist
{quote}

You can join this or another compatibility discussion (if you have not already done so).

p.s. sorry for the late reply.

> Apache ignite unable to connect to a minor upgrade version
> ----------------------------------------------------------
>
>                 Key: IGNITE-8427
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8427
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.3, 2.4
>            Reporter: Arvindo
>            Priority: Major
>
> We have a distributed cache cluster, say with 2.3.0 in the cluster. We have cache clients connecting to the cluster in client mode (clientMode=true). When we upgrade the cluster to 2.4.0 (minor version). The clients are unable to connect to the new cluster. Apache ignite is not following semantic versioning standard, forcing the clients to upgrade their binaries for minor upgrades.
> [semantic MINOR release version standards|https://semver.org/].



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