[
https://issues.apache.org/jira/browse/STORM-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17490475#comment-17490475
]
Richard Zowalla edited comment on STORM-3817 at 2/10/22, 7:46 PM:
------------------------------------------------------------------
Interesting. Looks odd to me, that the CI build approach is not affected. Maybe
you can remove the exclusion in your PR, so we can be sure it builds in an IDE
and in the CI (although you need the Travis fixes from the PR above).
I migrated the exclusion from an older Zookeeper PR, so I do not insist on this
"optimization" - so we can just drop it
was (Author: rzo1):
Interesting. Looks odd to me, that the CI build approach is not affected. Maybe
you can remove the exclusion in your PR, so we can be sure it builds in an IDE
and in the CI (although you need the Travis fixes from the PR above).
I migrated the exclusion from an older Zookeeper PR, so I do not insist on this
"optimization"
> Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x
> --------------------------------------------
>
> Key: STORM-3817
> URL: https://issues.apache.org/jira/browse/STORM-3817
> Project: Apache Storm
> Issue Type: Dependency upgrade
> Affects Versions: 2.3.0, 2.2.1
> Reporter: Richard Zowalla
> Priority: Major
> Fix For: 2.4.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Is there any possibility to upgrade the [shaded zookeeper version
> |https://github.com/apache/storm/blob/master/storm-shaded-deps/pom.xml#L64]
> from 3.4.14 to a newer version? Or are there any reasons for not doing an
> upgrade right now?
> I am doing some testing with Storm in a Java 17 environment and it looks like
> I am suffering from this Zookeeper specific issue present in 3.4.14:
> https://issues.apache.org/jira/browse/ZOOKEEPER-3779
> If necessary I can also provide a PR for an upgrade to 3.5.x, 3.6.x or 3.7.x
> UPDATE: Looks like curator depends on 3.5.x - so probably 3.5.x should be an
> option.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
