[
https://issues.apache.org/jira/browse/FLINK-24707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437245#comment-17437245
]
David Morávek commented on FLINK-24707:
---------------------------------------
Hi [~jadireddi], thanks for being interested in this ticket.
The approach you've outlined is basically correct, however we should still
bring up the end of support for ZK 3.4.x to the mailing list to see if there
are any objections. Also we should get some better reasoning about which
version of zookeeper we want to update to (are the versions bw compatible? can
we update to latest then?). Also zookeeper update would involve releasing a new
flink-shaded-zookeeper artifact.
It would be a good idea to address this ticket after FLINK-24543 is resolved
(it can be worked on simultaneously, it's more about the merge order). The
upgrade story could also lead to a nice simplification of the "fixes"
introduced in FLINK-24543 (we can not do this right away, because the fix needs
to be backported).
> Upgrade Curator framework dependecy.
> ------------------------------------
>
> Key: FLINK-24707
> URL: https://issues.apache.org/jira/browse/FLINK-24707
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: David Morávek
> Priority: Major
> Fix For: 1.15.0
>
>
> We want to upgrade curator to latest version, to avoid working around
> non-idempotent writes.
> https://issues.apache.org/jira/browse/CURATOR-584
> Main reason for not doing this in patch release as part of FLINK-24543 is
> that this effectively drops support for Zookeeper 3.4.x.
> The very last past release two 3.4.x branch was more then two years ago (2
> April, 2019) and there are already three newer minor versions available
> (3.5.x,3.6.x,3.7.x).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
