25.0 release notes: batch 3#13429
Conversation
2bethere
left a comment
There was a problem hiding this comment.
Made some comments, mostly about shuffling content around. Thanks for pulling this together.
I think the new format with links are great!
| ~ under the License. | ||
| --> | ||
|
|
||
| ## Query engine |
There was a problem hiding this comment.
I think we should have a highlight section here. The top 3 features I think we should highlight are:
- MSQ production ready
- String dictionary compression (Experimental)
- K8S native tasks (i.e. Run tasks on K8S without middle managers)
|
|
||
| ## Query engine | ||
|
|
||
| ### BIG_SUM SQL function |
There was a problem hiding this comment.
This should be moved to the BIG_SUM SQL extension section.
|
|
||
| https://github.com/apache/druid/pull/13102 | ||
|
|
||
| ### Added Compressed Big Decimal min and max functions |
There was a problem hiding this comment.
Same as this one. I think moving this along with the extension makes it clear they are all part of the same functionality.
|
|
||
| ### Metrics used to downsample bucket | ||
|
|
||
| Changed the way the MSQ task engine determines whether or not to downsample data, to improve accuracy. The task engine now uses the number of bytes instead of number of keys. |
There was a problem hiding this comment.
I suggest create a MSQ section to group all MSQ things together so that it's easier for people to skip they want to see other stuff.
| This release includes several improvements for querying: | ||
|
|
||
| * Exposed HTTP response headers for SQL queries (https://github.com/apache/druid/pull/13052) | ||
| * Added the `shouldFinalize` feature for HLL and quantiles sketches. Druid will no longer finalize aggregators when: |
There was a problem hiding this comment.
I think we need to update the query docs on sketches to describe this behavior and why we made this change.
For example, "Druid will not finalize if aggregator is on the outer level because ......."
|
|
||
|
|
||
|
|
||
| ### Kill tasks do not include markAsUnuseddone |
There was a problem hiding this comment.
This is also a behavior change.
|
|
||
| https://github.com/apache/druid/pull/13059 | ||
|
|
||
| ### Improved supervisor termination |
There was a problem hiding this comment.
This should be moved together with other supervisor idle stuff.
|
|
||
| https://github.com/apache/druid/pull/13064 | ||
|
|
||
| ### Improved metric reporting |
There was a problem hiding this comment.
This should go into metrics section.
|
|
||
| https://github.com/apache/druid/pull/13262 | ||
|
|
||
| ## Web console |
There was a problem hiding this comment.
Web console should be moved above extensions
|
|
||
| https://github.com/apache/druid/pull/13291 | ||
|
|
||
| ### Query history |
There was a problem hiding this comment.
This should move to MSQ section.
| The unused coordinator property `druid.coordinator.loadqueuepeon.repeatDelay` has been removed. | ||
|
|
||
| Use only `druid.coordinator.loadqueuepeon.http.repeatDelay` to configure repeat delay for the HTTP-based segment loading queue. |
There was a problem hiding this comment.
These two items should either be under the heading Segment assignment or a separate heading titled Segment load queue peon.
Co-authored-by: Kashif Faraz <kashif.faraz@gmail.com>
|
The only one I haven't added is #13365 from the milestone since the original PR is still open. |
Co-authored-by: Karan Kumar <karankumar1100@gmail.com>
|
@kfaraz I've added the start-druid script entry to the release notes, so we should be all caught up. |
| | `druid.coordinator.loadqueuepeon.type` for segment management | http | curator | | ||
| | `druid.indexer.runner.type` for the Overlord | httpRemote | local | | ||
|
|
||
| To use ZooKeeper instead of HTTP, change the values for the properties back to the previous defaults. |
There was a problem hiding this comment.
We should also mention that the Zookeeper based implementations for the above items are now deprecated and will be removed in subsequent releases.
|
|
||
| ## Operations | ||
|
|
||
| ### Deploying Druid |
There was a problem hiding this comment.
This item should be in the highlights.
|
|
||
| ### Deploying Druid | ||
|
|
||
| There is now a Python installation script available for Druid that simplifies deployments that don't fit the parameters of the singel-server profiles, such as the nano or micro-quickstart profiles. This `start-druid` script lets you override Druid settings to fit your needs. For more information, see [Single server deployment](https://druid.apache.org/docs/latest/operations/single-server.html). |
There was a problem hiding this comment.
The new script simplifies deployments for all cases, not just the ones that don't fit the existing single-server profiles. We could probably rephrase this section as follows:
| There is now a Python installation script available for Druid that simplifies deployments that don't fit the parameters of the singel-server profiles, such as the nano or micro-quickstart profiles. This `start-druid` script lets you override Druid settings to fit your needs. For more information, see [Single server deployment](https://druid.apache.org/docs/latest/operations/single-server.html). | |
| The new `start-druid` script greatly simplifies deploying any combination of Druid services on a single-server. It comes pre-packaged with the required configs and can be used to launch a fully functional Druid cluster simply by invoking `./start-druid`. For the experienced Druids, it also gives you complete control over the runtime properties and JVM arguments to have a cluster that exactly fits your needs. | |
| The `start-druid` script deprecates the existing profiles such as `start-micro-quickstart` and `start-nano-quickstart`. These profiles may be removed in future releases. For more information, see [Single server deployment](https://druid.apache.org/docs/latest/operations/single-server.html). |
@vogievetsky , does this capture our sentiments adequately?
There was a problem hiding this comment.
I moved this section to the highlights and also used the text from this comment.
Co-authored-by: Kashif Faraz <kashif.faraz@gmail.com>
|
Closing this as Druid 25.0 is released. |
Replaces #13357
This takes us up to November 23 (after the 25.0.0 branch was created)