docs: 34.0.0 release notes by 317brian · Pull Request #18231 · apache/druid

317brian · 2025-07-10T17:45:11Z

WIP. This is caught up to late June. I am working on getting the most recent commits added.

Need to work on the highlights entry for Dart

This PR has:

adarshsanjeev · 2025-07-21T08:47:46Z

+Dart specific endpoints have been removed and folded into SqlResource. [#18003](https://github.com/apache/druid/pull/18003)
+Added a new engine QueryContext parameter. The value can be native or msq-dart. The value determines the engine used to run the query. The default value is native. [#18003](https://github.com/apache/druid/pull/18003)
+
+MSQ Dart is now able to query real-time tasks by setting the query context parameter includeSegmentSource to realtime, in a similar way to MSQ tasks. [#18076](https://github.com/apache/druid/pull/18076)


We can also specify that this is the default mode for Dart queries. I might have missed this in the PR initially.

Lets add an example where we hit the sql resource with engine=msq-dart

kfaraz

left some suggestions

cryptoe · 2025-07-21T11:34:01Z

+[#18028](https://github.com/apache/druid/pull/18028)
+
+### Preferred tier selection 
+You can now configure the Broker service to prefer  Historicals on a specific tier. This can help ensure Druid executes queries within the same availability zone if you have Druid deployed across multiple availability zones.


Waiting on PR author for release notes : #18136 (comment)

cryptoe · 2025-07-21T11:35:07Z

+Dart specific endpoints have been removed and folded into SqlResource. [#18003](https://github.com/apache/druid/pull/18003)
+Added a new engine QueryContext parameter. The value can be native or msq-dart. The value determines the engine used to run the query. The default value is native. [#18003](https://github.com/apache/druid/pull/18003)
+
+MSQ Dart is now able to query real-time tasks by setting the query context parameter includeSegmentSource to realtime, in a similar way to MSQ tasks. [#18076](https://github.com/apache/druid/pull/18076)


Lets add an example where we hit the sql resource with engine=msq-dart

cryptoe · 2025-07-21T11:36:22Z


+#### SET statements
+
+The web console supports using SET statements to specify query context parameters. For example, if you include `SET timeout = 20000;` in your query, the timeout query context parameter is set. 


This should be a headline feature.
Lets add an example which hits the sql endpoint, executes dart, and has timeout set.

I can move this to the headline section. This entry is specifically about the web console support for SET though.

I added an example that hits the SQL endpoint, uses dart etc to the API one

Co-authored-by: Karan Kumar <karankumar1100@gmail.com> Co-authored-by: Kashif Faraz <kashif.faraz@gmail.com>

abhishekrb19 · 2025-07-22T03:45:33Z

+- `druid.manager.segments.killUnused.enabled` - Whether the feature is enabled or not
+- `druid.manager.segments.killUnused.bufferPeriod` - The amount of time that a segment must be unused before it is able to be permanently removed from metadata and deep storage. This can serve as a buffer period to prevent data loss if data ends up being needed after being marked unused.


Do you think it's worth mentioning what the defaults for these configs are? (false and P30D)

Co-authored-by: Abhishek Radhakrishnan <abhishek.rb19@gmail.com>

capistrant

added color to one new feature

capistrant

I know D32 technically deprecated java11 and hadoop ingest. but do we want to drive them home with big bold sections for deprecations in D34 to really drive this point home these things are going away sooner rather than later?

capistrant · 2025-08-07T16:01:13Z

I know D32 technically deprecated java11 and hadoop ingest. but do we want to drive them home with big bold sections for deprecations in D34 to really drive this point home these things are going away sooner rather than later?

Talked with @abhishekagarwal87 and he thought maybe we call out in these release notes that hadoop ingest/java11 remain deprecated and are planning to have support dropped in Druid 35 with an urge for community to migrate off

Co-authored-by: Lucas Capistrant <capistrant@users.noreply.github.com>

capistrant

I'm cool with latest state. Thank you for all the iterations and review cycles!

fix spellchecker

docs: 34.0.0 release notes

ec18e5e

github-actions Bot added the Area - Documentation label Jul 10, 2025

317brian marked this pull request as draft July 10, 2025 19:06

317brian added this to the 34.0.0 milestone Jul 14, 2025

july 9

7bdf76f

adarshsanjeev reviewed Jul 21, 2025

View reviewed changes

kfaraz reviewed Jul 21, 2025

View reviewed changes

cryptoe reviewed Jul 21, 2025

View reviewed changes

317brian and others added 3 commits July 21, 2025 15:45

Apply suggestions from code review

7a7c612

Co-authored-by: Karan Kumar <karankumar1100@gmail.com> Co-authored-by: Kashif Faraz <kashif.faraz@gmail.com>

updates

19d205b

address comment for 18121

f01ff0a

abhishekrb19 reviewed Jul 22, 2025

View reviewed changes

317brian and others added 2 commits July 22, 2025 10:07

Apply suggestions from code review

6fdb43f

Co-authored-by: Abhishek Radhakrishnan <abhishek.rb19@gmail.com>

add 17983

7f19f08

317brian commented Jul 23, 2025

View reviewed changes

Comment thread docs/release-info/release-notes.md Outdated

317brian added 3 commits July 23, 2025 14:19

Update docs/release-info/release-notes.md

6290287

july 23

234a694

fix typos

06c197d

317brian marked this pull request as ready for review July 29, 2025 19:22

317brian added 2 commits July 29, 2025 16:44

add last prs

16d1f70

cleanup

50033a6

317brian requested review from capistrant and cryptoe August 4, 2025 17:50

317brian commented Aug 6, 2025

View reviewed changes

Comment thread docs/release-info/release-notes.md

Update docs/release-info/release-notes.md

0357c5e

317brian commented Aug 6, 2025

View reviewed changes

Comment thread docs/release-info/release-notes.md

Update docs/release-info/release-notes.md

ae5e0c2

capistrant reviewed Aug 7, 2025

View reviewed changes

Comment thread docs/release-info/release-notes.md Outdated

capistrant reviewed Aug 7, 2025

View reviewed changes

Update docs/release-info/release-notes.md

31685b5

Co-authored-by: Lucas Capistrant <capistrant@users.noreply.github.com>

317brian commented Aug 8, 2025

View reviewed changes

Comment thread docs/release-info/release-notes.md Outdated

update hadoop blurbs

869c7ff

capistrant approved these changes Aug 8, 2025

View reviewed changes

capistrant reviewed Aug 8, 2025

View reviewed changes

Comment thread docs/release-info/release-notes.md Outdated

Update docs/release-info/release-notes.md

588347b

fix spellchecker

capistrant merged commit 0d51afd into apache:34.0.0 Aug 11, 2025
6 checks passed


		#### SET statements

		The web console supports using SET statements to specify query context parameters. For example, if you include `SET timeout = 20000;` in your query, the timeout query context parameter is set.

		- `druid.manager.segments.killUnused.enabled` - Whether the feature is enabled or not
		- `druid.manager.segments.killUnused.bufferPeriod` - The amount of time that a segment must be unused before it is able to be permanently removed from metadata and deep storage. This can serve as a buffer period to prevent data loss if data ends up being needed after being marked unused.

Conversation

317brian commented Jul 10, 2025

Uh oh!

adarshsanjeev Jul 21, 2025

Choose a reason for hiding this comment

Uh oh!

cryptoe Jul 21, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

kfaraz left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cryptoe Jul 21, 2025

Choose a reason for hiding this comment

Uh oh!

cryptoe Jul 21, 2025

Choose a reason for hiding this comment

Uh oh!

cryptoe Jul 21, 2025

Choose a reason for hiding this comment

Uh oh!

317brian Jul 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

abhishekrb19 Jul 22, 2025

Choose a reason for hiding this comment

Uh oh!

capistrant Jul 22, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

capistrant left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

capistrant left a comment

Choose a reason for hiding this comment

Uh oh!

capistrant commented Aug 7, 2025

Uh oh!

Uh oh!

capistrant left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

317brian Jul 21, 2025 •

edited

Loading