Hi all, I’d like to request that the following PR be considered for inclusion in the upcoming release:
https://github.com/apache/druid/pull/19231 This PR fixes an issue where remoteAddress is always null for JDBC/Avatica SQL queries. As a result, the sqlQuery/time, sqlQuery/bytes, and sqlQuery/planningTimeMs metrics, as well as request logs, currently do not contain the client address for JDBC queries. The change makes JDBC/Avatica behavior consistent with the HTTP SQL API and includes tests covering normal queries, failed queries, and prepared statements. Since this affects observability and request attribution for JDBC users, I would appreciate it if the PR could be reviewed and merged in time for the upcoming release. Thanks, Dongkyu On 2026/07/09 06:36:06 Kashif Faraz wrote: > Hello > > On the 9th of May, we released Druid 37.0.0 which included several exciting > features and improvements! > Sticking to the schedule for quarterly releases, we would like to start > preparing for the release of Druid 38.0 in the first week of August. > I am volunteering to be the manager for this release. > > We can use this thread to discuss any high-priority issue or critical > feature that must be included in Druid 38.0. > There are several features already tagged for Druid 38 such as clustered > segments, partial segment downloads, multi cluster K8s task runner, > prunable shard specs for appended segments and several perf improvements. > > The tentative date for the code-freeze is July 13. Apologies for the short > notice, but since we are already behind schedule, let's ensure that all > open PRs slated for Druid 38.0 are appropriately tagged and fully reviewed > by then. > > Regards > Kashif >
