Hi all, any updates regarding the PR?
Gruß Richard Am Mittwoch, dem 26.01.2022 um 09:54 +0100 schrieb Richard Zowalla: > Hi all, > > can anyone have a look please? > > It blocks running Storm on Java 17. > > Build passes (but requires the changes from > https://github.com/apache/storm/pull/3437 to fix the CI environment) > > Gruß > Richard > > Am Mittwoch, dem 12.01.2022 um 16:18 +0100 schrieb Richard Zowalla: > > Hi all, > > > > I have created a pull request to upgrade Zookeeper to 3.5.9, which > > fixes STORM-3817: > > > > https://github.com/apache/storm/pull/3431 > > > > If someone can have a look and merge this one, I would be very > > happy. > > > > In addition, I was thinking about an upgrade to 3.6.x or 3.7.x but > > "curator-4.3.0" depends on 3.5.x - this lead to some weird > > behaviour > > in the unit tests. Guess it is related to a incompatible curator / > > zookeeper combination 4.3.x vs. 3.7.x (3.6.x) combination. > > > > Upgrading curator to 5.x breaks exhibitor support and I don't know, > > if > > this is a commonly used and required feature. Therefore, I stick to > > zookeeper 3.5.9 as this fixes the problem reported in STORM-3817. > > > > As a newbie to Storm dev, I had some issues in setting up and > > running > > the build in an Ubuntu 20.04 desktop environment. Documentation is > > a > > bit outdated / tricky in this regard. If appreciated, I could > > contribute some documentation enhancements to get it back up on > > track. > > > > In the end I relied on an Ubuntu 16.04 server VM and used the build > > scripts targeting Travis CI to conduct a full build and to get some > > feedback on my changes. Build passed. It also passes for the Travis > > CI: https://github.com/apache/storm/runs/4790137021 > > > > Gruß > > Richard > > > > > > > > Am Montag, dem 10.01.2022 um 18:47 +0100 schrieb Richard Zowalla: > > > Hi all, > > > > > > I am new to the Storm community habits and might miss context / > > > information, so execuse my question: > > > > > > Are there any strict objections to upgrade zookeeper from 3.4.14 > > > to > > > 3.6.x or 3.6.x as proposed in STORM-3817 [1]? > > > > > > Specifically I am running into [2] running a storm cluster (in a > > > docker-based setup) with Java 17. > > > > > > I saw, that there was a PR a while ago [3], which was never > > > merged. > > > > > > If there are no strict objections (as I am new to the Storm > > > community > > > habits and might miss context / information ;-)), I could > > > probably > > > give > > > it a try and provide a PR. > > > > > > Happy to get some feedback! > > > > > > Gruß > > > Richard > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/STORM-3817 > > > [2] https://issues.apache.org/jira/browse/ZOOKEEPER-3779 > > > [3] https://github.com/apache/storm/pull/3017 > > > > > >
signature.asc
Description: This is a digitally signed message part
