[
https://issues.apache.org/jira/browse/BOOKKEEPER-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944088#comment-13944088
]
Flavio Junqueira commented on BOOKKEEPER-589:
---------------------------------------------
Can we fix it in the 4.2 branch so that we have an upgrade path like
4.2.*->4.2.3->4.3.0? I didn't quite understand what the problem is, so I can't
suggest anything more concrete than this right now.
> Release notes update for non-BC changes
> ---------------------------------------
>
> Key: BOOKKEEPER-589
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-589
> Project: Bookkeeper
> Issue Type: Sub-task
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Priority: Blocker
> Fix For: 4.3.0
>
>
> 4.3.0 client will not be able to connect to 4.2.0 servers, due to something
> stupid in the protocol version handling. 4.2.0 and lower will blindly reject
> any messages which have a protocolVersion higher than that it's current
> version, even if the data format has not changed. The release notes should
> reflect this. Also, think about how the protocolVersion is used some more.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
