All Products
Search
Document Center

ApsaraDB for ClickHouse:Release details of ApsaraDB for ClickHouse Enterprise Edition V24.10

Last Updated:Jun 17, 2026

ApsaraDB for ClickHouse Enterprise Edition V24.10 introduces time alignment functions, enhanced array operations, refreshable materialized views in replicated databases, and a refactored Dynamic data type.

New features

  • The toStartOfInterval function now supports time alignment with a custom starting point, compatible with the time bucketing feature of TimescaleDB and PostgreSQL. You can align date or timestamp values to a specified interval.

  • The arrayZipUnaligned and arrayElementOrNull functions are added, improving Spark compatibility and array operation flexibility.

  • The tupleElement(expr(), 'name') syntax is now supported. You can process named tuples by using expressions in the expr().name format, which enhances JSON processing capabilities.

  • Refreshable materialized views are now supported in replicated databases.

  • The Dynamic data type is refactored. When the limit of the Dynamic data type is reached, new data types are stored in binary format as separate subcolumns instead of being converted to the String type.

  • The MongoDB driver is upgraded to the new mongocxx driver, which removes support for the old protocol, adds support for all MongoDB data types, and enables execution of WHERE and ORDER BY clauses on the MongoDB side.

  • Query caches can be deleted by tag. Example: SYSTEM DROP QUERY CACHE TAG 'abc'.

  • Enhanced support for reading Iceberg tables and improved compatibility with Iceberg data sources.

Performance optimization

  • The progress-table parameter is added to display real-time changing metrics during query execution. Press the Space key to show or hide the progress table.

  • The input_format_json_empty_as_default setting is added. When enabled, empty fields in JSON inputs are treated as default values, improving JSON processing flexibility.

Breaking changes

  • The SETTINGS clause can now be added before FORMAT in a UNION query with subqueries. If multiple SETTINGS clauses are specified, the clause closest to a subquery takes effect.

  • When the limit of the Dynamic data type is reached, new data types are stored in binary format as separate subcolumns instead of being converted to the String type.

Fixed issues

  • Fixed an issue where enabling optimize_functions_to_subcolumns caused a column type error and prevented the LowCardinality data type from being processed.

  • Fixed an issue where SQL queries prematurely terminated due to inaccurate memory statistics.

  • Fixed an issue where JSON data could not be parsed when empty fields were used.

  • Fixed an issue where query caches could not be accurately deleted in specific cases.

  • Fixed an issue where the lack of support for sparse delete operations in MergeJoin could cause data merging issues.