cryptoe commented on code in PR #17872: URL: https://github.com/apache/druid/pull/17872#discussion_r2046603333
########## docs/release-info/release-notes.md: ########## @@ -65,6 +115,12 @@ This section contains detailed release notes separated by areas. #### Other web console improvements +- Added the ability to multi-select in table filters and added suggestions to the **Status** field for tasks and supervisors as well as service type [#17765](https://github.com/apache/druid/pull/17765) +- The MERGE INTO keyword is now properly highlighted and the query gets treated as an insert query [#17679](https://github.com/apache/druid/pull/17679) Review Comment: This need not be called out . ########## docs/release-info/release-notes.md: ########## @@ -57,6 +57,56 @@ For tips about how to write a good release note, see [Release notes](https://git This section contains important information about new and existing features. +### Increase segment load speed + +You can now increase the speed at which segments get loaded on a Historical by providing a list of servers for the Coordinator dynamic config `turboLoadingNodes`. For these servers, the Coordinator ignores `druid.coordinator.loadqueuepeon.http.batchSize` and uses the value of the respective `numLoadingThreads` instead. Please note that putting a Historical in turbo-loading mode might affect query performance since more resources would be used by the segment loading threads. + +[#17775](https://github.com/apache/druid/pull/17775) + +### Overlord APIs for compaction (experimental) + +You can use the following Overlord compaction APIs to manage compaction status and configs. These APIs work seamlessly irrespective of whether compaction supervisors are enabled or not. + +For more information, see [Compaction APIs](#compaction-apis) + +[#17834](https://github.com/apache/druid/pull/17834) + +### Scheduled batch ingestion (experimental) + +You can now schedule batch ingestions with the MSQ task engine by using the scheduled batch supervisor. You can specify the schedule using either the standard Unix cron syntax or Quartz cron syntax by setting the `type` field to either `unix` or `quartz`. Unix also supports macro expressions such as `@daily` and others. + +Submit your supervisor spec to the `/druid/v2/sql/task/` endpoint. + +The following example scheduled batch supervisor spec submits a REPLACE query every 5 minutes: + +```json +{ + "type": "scheduled_batch", + "schedulerConfig": { + "type": "unix", + "schedule": "*/5 * * * *" + }, + "spec": { + "query": "REPLACE INTO foo OVERWRITE ALL SELECT * FROM bar PARTITIONED BY DAY" + }, + "suspended": false +} +``` + +[#17353](https://github.com/apache/druid/pull/17353) + +### Improved S3 upload + +Druid can now use AWS S3 Transfer Manager for S3 uploads, which can significantly reduce segment upload time. To use this feature, add the following configs to your `common.runtime.properties`: Review Comment: This is turned on by default. Adjusted the PR description. cc @suraj-goel ########## docs/release-info/release-notes.md: ########## @@ -57,6 +57,56 @@ For tips about how to write a good release note, see [Release notes](https://git This section contains important information about new and existing features. +### Increase segment load speed + +You can now increase the speed at which segments get loaded at the cost of query performance by providing a list of servers for the Coordinator dynamic config `turboLoadingNodes`. For these servers, the Coordinator ignores `druid.coordinator.loadqueuepeon.http.batchSize` and uses the value of the respective `numLoadingThreads` instead. Review Comment: @kfaraz should we mark this as experimental. That way we can change stuff later down the line ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
