Recently the

CompressionUtilsTest#testGunzipBug()

test has been flaky on JDK 21. All PR merges into

master

have failed with this in the past 3 weeks (refs: 1, 2, 3). This seems to coincide with the JDK 21 upgrade, it seems CI is pulling the latest version 21.0.9 and it’s possible that the underlying JDK bug has been fixed in this version. The issue appears only on

master

since PRs don’t currently run tests with JDK 21. From what I can tell, these tests don’t actually test Druid’s

CompressionUtils

internals but were likely added to track the historical JDK bug (they still pass on jdk 17). Should we consider removing these tests

testGunzipBug

,

testGunzipBugWorkaround

and

testGunzipBugStreamWorkaround

? Or disable them when running on JDK 21 if they still serve a purpose?

Hi folks, wondering if v35 release notes are being added? I see the release tag on GH, but not the notes

Hi team. Was wondering if there is any reason why editing load rules does not allow for deletion of entries for datasources? Our use case has a high throughput of datasources being added and deleted with specific load rules so the load rules file tends to get updated. Since there is no delete option for load rules : this causes the file to get bloated with "deleted-datasource":[] type of entries. Lmk if I've missed something here.

👋 Would appreciate some eyes on some issues I've outlined: • https://github.com/apache/druid/issues/18716 • https://github.com/apache/druid/issues/18738 We're seeing this more and more in our production clusters and would like to know what community thinks is best path forward.

Small QoL improvement, whenever someone gets a chance: https://github.com/apache/druid/pull/18762

Hi Team, I would like to ask one question

image.png

I'm using Imply UI 2.0 -> but it seems the comparison feature with specific time didn't work well like version 1.0

For example When filtering 10-12/Nov vs a start day 3/Sept, it didn't compare day 10/Nov to day 3/Sept and day 11/Nov to day 4/Sept

is it a bug or i'm using in a wrong way ?

please help me

Looks like some tests in KubernetesTaskRunnerDirectModeDockerTest and KubernetesTaskRunnerCachingModeDockerTest are consistently failings ?

The`KubernetesTaskRunnerDirectModeDockerTest` is failing in our CI because the druid-operator chart is unavailable. Related to https://github.com/datainfrahq/druid-operator/issues/259 Do we know if there’s a workaround for this chart issue specific to this test? Tagging a few folks to get their thoughts cc: @Adheip Singh @kfaraz @Gian Merlino

With an increased adoption of AI tools, what do folks think about https://github.com/apache/druid/pull/19084? It's currently just a placeholder

👋 at our company we'd like to add support for GCS-based warehouses in the iceberg extension. to make that work properly i think there are a couple changes needed: 1. add an implementation of an

InputSourceFactory

for GCS and make it available to the iceberg extension 2. bump iceberg internally to 1.7+ in order to pick up this credential vending change i'd like to put in patches for these, i assume it would be better to do them as two separate patches? i also saw there's an open issue for iceberg integration testing which i can try to tackle; is there a preferred integration testing approach that already exists (testcontainers, etc)?

@Razin Bouzar I'm seeing an issues with the generated code at HEAD - 🧵

Hello, I am new to open source contribution (I have 4 years of working experience). I have used apache druid in my past organisation. I want to contribute to this project. will somebody please guide me the steps to contribute. I see there are some active issues, but in some issues I saw the issue raiser himself has raised a PR. So, I am not really sure which issue to pick for working. Any help is appreciated.

@Clint Wylie @Gian Merlino RE https://github.com/apache/druid/pull/19393#issuecomment-4361242858 🧵

Hi team, Please review : https://github.com/apache/druid/pull/19285

👋 I proposed this PR to remove some unnecessary dependency for HDFSInputSource (GH issue) Can I approval for the workflows run and a review to the contribution? Feel free to assign the GH issue to me

Hi team, Kafka Upgrade 4.2.0 : https://github.com/apache/druid/pull/19441 Please review and lets get it merged, this is needed for Queue Semantics implementation https://github.com/apache/druid/pull/19311

Hey team, Can I ask to re-trigger

docker-tests

on these 2 PRs? https://github.com/apache/druid/pull/19432 https://github.com/apache/druid/pull/19434 Both are failing for

The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

.

docker-tests

seems a bit flaky: just a re-rerun makes them successful

@Clint Wylie @Gian Merlino wanted to get your thoughts on a few PRs: • https://github.com/apache/druid/pull/19431 • https://github.com/apache/druid/pull/19413

Hey! Anyone available to have a look to this PR? https://github.com/apache/druid/pull/19432

Hey all , wanted a general opinion . I recently started working with druid . our compaction service config is like maxRows = 5 million , but we also hash by OrgId . it was working well but we now have a big org , adding around 5 billion logs a week . and their spikes are also huge like 20 million in one hour and maybe 200 million in other . so basically wanted to optimize for skewness in this case . I was thinking of two things , first lowering segment partition from day to hour and second adding a secondary dimension like Control Plane Id would love to know if anyone had similiar experiences and has better explored any better options . also raised an Issue for a feat I would want to add for warning on such skewed cases : https://github.com/apache/druid/issues/19573 , would love views on that as well .

Thoughts on https://lists.apache.org/thread/ho7rc5dtkfk0m7vk07y1mgbxfb4vrdrr? cc: @Gian Merlino @Clint Wylie

Hello there 👋 Can someone review this small PR to add support to advertise druid on different port than the listening port, please? cc: @PANKAJ KUMAR

is there a place where I can find a list of sample databases for druid ? Specifically supply chain or medical?

Hey there! Can you have a look to this PR? github.com/apache/druid/pull/19670 In agreement with stackable, we would like to add druid-opa-authorizer to extension-contrib.

Hi team 👋 I have created an issue here to shard the priorityQueue on historicals as it has been causing lock contention on the historical nodes I have captured the details here- github.com/apache/druid/issues/19937 could you please help me determine the feasibility of the proposal then I can work on the change? cc: @kfaraz @Frank Chen