Altinity Stable® Build for ClickHouse® 24.3

Altinity Stable® Build for ClickHouse® 24.3 is now available! As Altinity users are aware, Altinity Stable Builds are based on ClickHouse Long Term Support releases and maintained for three years. We build them for organizations who value stable operation without major upgrades for long periods of time. 

Version 24.3 Release Summary

It has been a while since we certified Altinity Stable Build for ClickHouse® 23.8. Since then, many good things have happened in the ClickHouse GitHub project. More than 300 contributors from companies all around the world submitted 3154 pull requests with new features and improvements. We spent the last four months testing the build and tracking fixes merged to the 24.3 LTS branch. We also collected early adopter feedback on upgrades as well as feature changes that affect production use. As of version 24.3.5 we are confident in certifying 24.3 as ready for use. 

Detailed release notes for Altinity Stable Build 24.3 are available on the Altinity Documentation Site. There are a lot of new features, but also many behavior changes, so check the release notes carefully before upgrading. The most important change is that the new Analyzer is enabled by default. While this is a significant step forward for ClickHouse SQL compatibility, it introduces changes that may cause regressions in queries. Please test upgrade carefully and read the known limitations. Also check the ClickHouse® Upgrade E-book, which provides guidelines for upgrading ClickHouse databases.

Differences between this build and upstream official builds

Like upstream builds, Altinity Stable builds for ClickHouse are open source and are based on upstream LTS versions. Altinity Stable Build version 24.3.5 is based on upstream 24.3.5.46-lts, but we have additionally backported several fixes:

• Fix the crash loop when restoring from backup is blocked by creating an MV with a definer that hasn’t been restored yet. (#64595 by @pufit)
• Fix moving partition to itself (#62524 by @helifu)
• Fix detection of number of CPUs in containers. In the case when the ‘root’ cgroup was used (i.e. name of cgroup was empty, which is common for containers) ClickHouse was ignoring the CPU limits set for the container. (#66237 by @filimonov)

Let’s install!

Altinity Stable Linux packages can be found at https://builds.altinity.cloud. Altinity Stable build images are available as altinity/clickhouse-server:24.3.5.47.altinitystable on Docker Hub. 

For information on installing Altinity Builds, see the Altinity Stable® Builds Install Guide. 

Please contact us at info@altinity.com if you experience any issues with the upgrade.

Want more information about Altinity Stable Builds? 

Check out our blog article on the upgrade philosophy behind Altinity Stable Builds and how it differs from official ClickHouse builds. Altinity supports both builds, so you can choose whichever is best for you!