The lifecycle policy for ApsaraDB for ClickHouse Community-Compatible Edition covers the changes that ApsaraDB for ClickHouse Community-Compatible Edition undergoes at each lifecycle stage, the business impact, and the product evolution plan. Use this information to plan version upgrades and avoid risks.
Background information
The ClickHouse open source community continuously releases new versions with faster performance, improved security, and additional features. At the same time, the community is reducing support for older versions. It updates the Long-Term Support (LTS) version every six months and maintains only the current and previous LTS versions. Continuing to use older versions may expose you to security and stability risks.
Current lifecycle of the ApsaraDB for ClickHouse Community-compatible Edition
To give you more time to upgrade major versions of the ApsaraDB for ClickHouse Community-compatible Edition, ApsaraDB for ClickHouse typically extends the maintenance period by one year beyond what the open source community offers. After this extended period ends, support for the expired engine versions is discontinued.
Services for existing instances that run an unsupported version will continue to operate. You can still perform operations such as upgrading or downgrading instance specifications, renewing, and unsubscribing.
Unsupported versions have the following limitations:
New purchases are disabled.
Feature iterations and upgrades are discontinued.
Engine version updates are discontinued.
Fixes for vulnerabilities and bugs are discontinued, except for critical ones.
The following table lists the end-of-support dates for each version of the ApsaraDB for ClickHouse Community-compatible Edition. Use this information to choose a suitable version when you create, migrate, or upgrade instances.
Some dates in the table are estimates and may be updated before the end-of-life (EOL) date or before support for the community-compatible version of ApsaraDB for ClickHouse is discontinued. The actual extended maintenance period is subject to end-of-sale announcements and notifications.
Version | Community release date | ApsaraDB for ClickHouse Community-compatible Edition release date | Community end-of-support date | Estimated ApsaraDB for ClickHouse Community-compatible Edition end-of-support date |
19.15 | October 1, 2019 | December 12, 2019 | October 1, 2020 | April 16, 2021 |
20.3 | May 23, 2020 | June 4, 2020 | May 23, 2021 | October 28, 2022 |
20.8 | October 9, 2020 | November 26, 2020 | October 9, 2021 | October 28, 2022 |
21.8 | August 12, 2021 | November 26, 2021 | August 12, 2022 | April 24, 2024 |
22.8 | August 18, 2022 | October 28, 2022 | August 18, 2023 | January 15, 2025 |
23.8 | August 31, 2023 | March 7, 2024 | October 26, 2024 | January 31, 2027 |
25.3 | March 20, 2025 | July 17, 2025 | March 20, 2026 | No plan yet |
26.3 | March 26, 2026 | Estimated July 31, 2026 | N/A | No plan yet |
Service commitments and suggestions
Compatibility
The ApsaraDB for ClickHouse Community-compatible Edition does not guarantee compatibility between major versions. However, we make every effort to maintain compatibility of syntax, interfaces, and features across major versions. Any potential incompatibilities are communicated through documentation or after-sales service. For more information, see Community-compatible Edition.
The ApsaraDB for ClickHouse Community-compatible Edition guarantees compatibility of syntax, interfaces, and features between minor versions within the same major version. Upgrade to the latest minor version of your current major version to ensure compatibility.
Bugs
If you are not using the latest version, upgrade to a newer major or minor version to apply bug fixes based on the compatibility commitment. For information about the latest minor version, see Community-compatible Edition.