We are delighted to announce that Altinity Stable Release™ is updated to 184.108.40.206. The release includes several dozen bug fixes not present in the previous 220.127.116.11, the most important ones are:
- Fixed a bug that prevented attaching Materialized Views to system tables
- Fixed incorrect behavior of if function with NULLs
- Fixed segfaults in rare cases
- Fixed a bug that prevented predicate pushdown for queries using WITH clause
- Fixed SIGSEGV in Kafka engine when broker is unavailable
- Fixed a bug leading to ‘block structure mismatch’ error for queries with UNION and JOIN
- Fixed TTL processing logic to process all partitions in one run
- Fixed a bug of parsing of row policies from configuration files that could result in missing policies sometimes
- Fixed a bug with ALTER TABLE UPDATE could produce incorrect results when updating Nullable columns
- Fixed a bug with codecs not working properly for MergeTree compact parts
There were few performance improvements as well:
- Server startup time has been reduced by parsing metadata in parallel
- Improved performance of primary key analysis for LowCardinality columns. That was a performance regression introduced in 20.3
- Improved performance of queries with large tuples and tuples used in primary key
The development team continues to improve the quality of newer releases as well. 20.6 is a new stable release candidate, we plan to certify it in the next few weeks. We are using it extensively in our benchmarks and internal R&D projects already. 20.8 looks promising as well if you are looking for the latest features.
Updated RPM packages for Altinity Stable Release can be found in the Altinity Stable Repository. The ClickHouse repository can be used for DEB packages but check version numbers carefully. Remember that you can also find Altinity release descriptions in our blog using the ‘Releases’ tag.
Please reach us at [email protected] if you have any questions regarding this stable release.