[
https://issues.apache.org/jira/browse/ZOOKEEPER-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820945#comment-13820945
]
Germán Blanco commented on ZOOKEEPER-1808:
------------------------------------------
I am assuming that we only need to ensure that the rolling upgrade works for
official releases (3.4.5, 3.4.5, 3.5.0 ...) and not e.g. between an snapshot of
trunk and 3.5.0.
As I see it, in 3.5.0 the checks should be modified in that now there will also
be a "backCompatibility40" (strict comparison length == 40) that includes the
version number. Configuration information will follow the version number. For
any message including the version number, this version number is what needs to
be checked in order to parse any message content above the length of 40.
> Add version to FLE notifications for 3.4 branch
> -----------------------------------------------
>
> Key: ZOOKEEPER-1808
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1808
> Project: ZooKeeper
> Issue Type: Sub-task
> Reporter: Flavio Junqueira
> Assignee: Flavio Junqueira
> Fix For: 3.4.6
>
> Attachments: ZOOKEEPER-1808.patch, ZOOKEEPER-1808.patch,
> ZOOKEEPER-1808.patch, ZOOKEEPER-1808.patch, ZOOKEEPER-1808.patch,
> ZOOKEEPER-1808.patch, ZOOKEEPER-1808.patch
>
>
> Add version to notification messages so that we can differentiate messages
> during rolling upgrades. This task is for the 3.4 branch only.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
