This message was deleted.

I saw a recent Curator patch being merged related to this issue: apache/curator#433. Maybe it is time to upgrade Curator? I could see why Druid community have no love towards Curator.

There are quite a few fixes planned for curator 5.4.0 that I am excited to try out once it's released. 538 as you mentioned as well as https://issues.apache.org/jira/plugins/servlet/mobile#issue/CURATOR-649 which look like they were both fixed by the same commit.

Does Maven have a concept of vendoring the source code like in Go? Curator codebase looked small. If vendored inside Druid, Druid devs can fix Curator NPE immediately without waiting on a new release. Just a small thought I have.

You could build Druid yourself specifying the

SNAPSHOT

artifact from Curator.

Usually, most projects, as well as Druid (I think), tend to avoid forking the code. Mostly because original code and forked code can diverge over time. So it carries some maintenance overhead. Then we will run into problems that non-standard techniques generally run into. E.g. if there is a CVE in the curator library, we won't be notified because we have our own fork instead of using a released version.