Lifecycle policy
The Imply Product includes Imply's distribution of Apache Druid® , Pivot, Clarity, Imply Manager, and associated artifacts included in the Imply product distribution.
As of November 2020, Imply releases fall into one of two categories: Long Term Support (LTS) and Short Term Support (STS).
Imply Product Long Term Support (LTS) releases are complete, stable versions of our products. They are subject to general bug fixes for one year and to security bug fixes for two years after release, but do not receive new features or feature enhancements. They are best suited to production environments that require stable operation and do not require the latest features.
Releases that are not subject to long term support—that is, Short Term Support (STS) releases—include the latest features, including experimental features.
Regularly scheduled LTS and STS versions are released quarterly in alignment with open source Apache Druid releases. Critical bug fixes or security patches are issued as hotfixes against both release lines as needed between release cycles.
End-of-support dates
| Version | General support end | Security support end |
|---|---|---|
| 2025.01 LTS | January 28, 2026 | January 28, 2027 |
| 2024.01 LTS | January 25, 2025 | January 25, 2026 |
LTS end-of-support dates
| Version | Support end date |
|---|---|
| 2023.01 | January 25, 2025 |
| 2022.01 | January 31, 2024 |
| 2021.01 | January 26, 2023 |
| 4.x | January 26, 2022 |
| 3.x | October 12, 2021 |
More information
Also see the previous policy at Terms and conditions for maintenance and support services.
Supported upgrade paths
STS to STS upgrades
For regularly scheduled STS releases, you can only upgrade to a new version from the STS version that immediately precedes it. For example, to upgrade to the third quarter release, you must already be on the second quarter release.
LTS to LTS upgrades
LTS patch upgrades
You can upgrade to any LTS patch version that is released for that LTS. For example, you can upgrade to 2022.01.06 LTS from any earlier version of the 2022.01 LTS release train.
Upgrade to the next LTS
Upgrading to the next LTS release year from the previous LTS release year requires you to upgrade to the first LTS release of the target LTS release.
Then, you can upgrade to a specific patch number.
The following example shows the upgrade path from the 2024.01 LTS release to the 2025.01 LTS release:
2024.01.13 to 2025.01.01 2025.01.01 to 2022.01.NN
Switch between LTS and STS releases
Although you can switch between the two release types, certain conditions must be met based on your source and target release train.
The 2025 LTS and STS releases handle queries that involve Booleans and null values differently. Review the LTS upgrade and downgrade notes to familiarize yourself with how your query results could change.
LTS to STS release
To switch from an LTS release to an STS release, you can upgrade to an STS release of the same quarter.
Another option is to continue to upgrade your LTS release and wait until the initial release of the STS and LTS for the next year.
STS to LTS release
Switching to LTS releases from STS releases can only be done in January when LTS and STS releases coincide.
For example, this is the upgrade path if you are on 2024.09 STS:
- 2024.09 STS to 2024.10 STS
- 2024.10 STS to 2025.01 LTS