Druid 24.0.1 Inaccurate Release Notes (at least one missing patch)

Hi all, Regrettably, I was not able to participate in 24.0.1 release validation and voting this time. As I was packaging up the new release 24.0.1 today, I noticed that at least one patch is missing from the release when compared to the release notes. https://github.com/apache/druid/pull/13138

Limitations of automated unused segment kill logic (Issue #10876 and PR #10877)

ing open PRs in the Druid project, so I'm more than happy to set up a "review for a review" type of agreement with someone who is also working on a new change. Feel free to reach out directly via email or a comment on my PR if you have something you are working to get reviewed. Thank you, Lucas Capistrant

Re: Log4j vulnerability - hotfix?

Since it is “critical” severity, I think it would be a good idea to seriously consider pushing out a minor version of 0.22.x. Especially since the mitigation strategy outlined in the CVE is not available in the log4j version that exists today in the current stable release. There is past precedent

Re: [VOTE] Release Apache Druid 0.21.1 [RC1]

+1 (binding) src - Proper NOTICE and LICENSE files present - Verified .asc signatures and .sha512 checksums - git.version file is present and correct - mvn build passed with unit tests - mvn rat checks passed - ran cluster with built binaries and executed native batch ingestion followed by basic

Re: Propose a scheme for Coordinator to pull metadata incrementally

Hey Benedict, Adding on to what Samarth says in their reply, could you provide some more context on this one to help the group understand more about your issue: - Is this the area of the code that you are saying in non-performant? Link

Re: Regarding the 0.21.0 release

I lean towards the option to do 2 releases. Operators can feel more confident about stability of 0.21.0 if their upgrade is coming up. If we choose to do multiple releases - To avoid operators having to upgrade large clusters twice in close proximity, we should do our best to communicate the

Re: Forbidding forced git push

+1 from me. I completely agree that it creates pain for reviewers. I think it’s important to keep reviewing as frictionless as possible to help maintain community involvement On Fri, Jan 15, 2021 at 3:00 PM Jihoon Son wrote: > Hi all, > > The forced git push is usually used to make the commit

Proposal Discussion Plug: #9816 Guild Replication

Hi all, I have created a proposal, https://github.com/apache/druid/issues/9816, that regards adding new functionality to the Druid segment replication infrastructure. I wanted to share it in the dev list to try and get some more eyes on it and drive discussion. I won't repeat too much of what

questions regarding merging approved PRs into master

Hi all, As a newish committer, I wanted to search out some quick clarification before I merge a PR into master for the first time in the Druid project. q1: Is the "squash and merge" option the preferred merge pattern? I see it is the default option when viewing a PR, but I felt double checking

Re: Pull #9224 - Druid Coordinator Pause Feature

ly one > > we have been looking for for quite a while in the several clusters I > > manage. I'm excited to see this capability added to the system. > > > > Will > > > > On Mon, Jan 20, 2020, 1:55 PM Lucas Capistrant < > capistrant.lu...@gmail.com > > >

Pull #9224 - Druid Coordinator Pause Feature

riting some time of integration test that flexes this code path. Despite the changes perceived simplicity, it would be nice to have something there. Thanks! Lucas Capistrant