We’re happy to announce our latest release, Druid 0.9.2!
Druid 0.9.2 contains hundreds of performance improvements, stability improvements, and bug fixes from over 30 contributors. Major new features include a new groupBy engine, ability to disable rollup at ingestion time, ability to filter on longs, new encoding options for long-typed columns, performance improvements for HyperUnique and DataSketches, a query cache implementation based on Caffeine, a new lookup extension exposing fine grained caching strategies, support for reading ORC files, and new aggregators for variance and standard deviation.
You can download the release here:
Release notes are at:
Thanks to everyone who contributed issues, docs, and code!
This is a really great update, thanks to everyone for this work!
Wanted to know if we could use same old config files from version 9.1.1 or there are any config values that changed (or maybe added).
I’ve been reading how to upgrade from 9.1.1 to 9.2 but I couldn’t find if it is safe to use old config files.
The release notes have details on upgrading: https://github.com/druid-io/druid/releases/tag/druid-0.9.2, see the “Updating from 0.9.1.1” section. You can assume that anything not specifically mentioned in that section will continue to work as before. In this case, the only configurations affected in this release are for QTLs, where the druid-namespace-lookup extension, which was deprecated in 0.9.1 in favor of druid-lookups-cached-global, has been removed in 0.9.2.
If you want to use some of the new 0.9.2 features though (including the new groupBy engine) then you will need to add some configs. You can follow links from the release notes to the docs for any of the new features you’re interested in.
See https://github.com/druid-io/druid/releases/tag/druid-0.9.2 in the Updating from 0.9.1.1 section
As a general rule any configuration options for stock druid with non-experimental features are fully supported between minor version updates, such as 0.9.x --> 0.9.x+1
Any configuration options for stock druid with non-experimental features that must be changed, require a bigger version update, such as 0.9.x --> 0.10.0
Note that in general roll forwards / backwards between two tangential versions is fully supported, such as going back and forth between 0.9.2 and 0.9.1.1, but sometimes larger jumps in versions are not able to be done seamlessly, such as between 0.8.2 and 0.9.2, and are not supported. Only sequential updates through releases are officially supported by the druid community.
Any configuration options that should be changed, even for experimental features, are called out in the release notes and have the instructions for what needs to be changed under what circumstances.
We are not perfect though, and any violation of proper awareness of configuration changes is considered a bug.
Thanks a lot guys for your feedback. The upgrade was successful and didn’t have any problems on the roll-out. It’s good to have more information about how to perform upgrades, will be useful in the future.