Repository navigation
Releases
26.6.8.20004 Altinity Antalya
26.6.8.20004 Altinity Antalya as compared to v26.6.8.20003.altinityantalya
Critical Bug Fixes
- Fixed CVE-2026-116366
Packages
Available for both AMD64 and Aarch64 from https://builds.altinity.cloud/#altinityantalya as either .deb, .rpm, or .tgz
These binaries include additional changes whose source is temporarily withheld pending coordinated security disclosure. The public tag identifies the public source baseline and does not contain all changes used to build these binaries.
Docker images
Available for both AMD64 and Aarch64: altinity/clickhouse-server:26.6.8.20004.altinityantalya
26.6.8.20003 Altinity Antalya
26.6.8.20003 Altinity Antalya (d21bf1d) as compared to v26.6.8.20002.altinityantalya (20d68b0d4aea62a8977f154edd004e553fc5d034)
New Features
- Implement iceberg v3 feature when the transformations are created in multiple columns,
source-idsdata is stored in the manifest. This PR will read iceberg tables created withsource-idsand not throw an error. (#2318 by @subkanthi) - Forward auth tokens to data lake catalogs (#2329 by @zvonand)
- Implement bin-packing
ReWriteFilesoperation that Identifies small data files below a target size threshold(defined in Settings), groups them and merges to a large file, creates a snapshot that marks the old ones as DELETED and the new larger merge file as ADDED. Leave all other files, manifests, and history untouched (#2420 by @subkanthi) - Add Iceberg v3 statistics (next-seq-num and first_row_id). This PR allows to write those stats. Follow up to #2308 which included functionality to read both the stats columns. (ClickHouse#116171 by @scanhex12 via #2456)
Performance Improvements
- Reduce number of Puffin file HEAD requests (#2419 by @UnamedRus)
Improvements
- Fixed
ALIAScolumns read throughDistributed,MergeoverDistributed, and Hybrid tables. AJOINwhose two sides declare a same-namedALIAScolumn failed withMULTIPLE_EXPRESSIONS_FOR_ALIAS; reading anALIAScolumn of aMergetable over aDistributedchild failed withNOT_FOUND_COLUMN_IN_BLOCKor returned defaults; reading anALIAScolumn of a Hybrid table from inside a subquery failed withTHERE_IS_NO_COLUMN; and anALIAScolumn referenced from inside a lambda over aDistributedtable failed on the shard. (#2409 by @mkmkme) - Enable Google as IdP for token-based authentication (#2499 by @zvonand)
- Add new functions
addVarUIntLengthPrefix,removeVarUIntLengthPrefix, andtoVarUIntto add or strip the length prefix so raw Apache DataSketches can be read asuniqApacheHLLstates and exported back. New optional third parameterestimatorforuniqApacheHLLwith values 'DEFAULT' or 'COMPOSITE'. 'COMPOSITE' gives a result not dependent on the order of inserts and merges. (#2544 by @UnamedRus) - Accept unsigned to signed promotion when possible (#2559 by @arthurpassos)
SYSTEM CAS DROP POOL MEMBERkeeps the member'sowner,epochandmountobjects, tombstones the owner before draining and verifies the retirement. Its result columnslot_removedis renamedmember_retired, andnamespaces_pending_gcis appended. Every CAS mount re-reads its owner after claiming its slot. Writer-epoch allocation is unique between same-uuid processes, and S3 staging keys carry the writer epoch. A clean CAS shutdown no longer skips its farewell when the stop races the start of a lease renewal. A decommission whose tombstone outcome is unknown no longer writes its clean farewell, so the member restarts only after GC fences its slot. (#2567 by @filimonov)- A CAS server whose
server_root_idwas decommissioned withSYSTEM CAS DROP POOL MEMBERnow comes back on its next start as an empty member, with the same or a new server uuid, instead of being refused.system.cas_mountsshows a decommissioned member asretired, with a newretirement_verifiedcolumn. (#2574 by @filimonov) - CAS blob publication logs the first failed attempt at Information instead of Warning, so a single retried failure no longer reaches clients that request warning-level logs. (#2594 by @filimonov)
- CAS GC no longer fences a mount whose token it watched for less than the observation threshold after a slow walk to the slot: the first sighting is dated after the read that returned the token (#2509 by @filimonov)
- The CAS sentinel probe returns its last inconclusive outcome instead of throwing when a retry pause ends exactly on the policy deadline (#2510 by @filimonov)
- A server memory limit no longer ends the CAS mount lease renewal thread; the conditional PUT of a CAS control-plane write runs on the calling thread with a buffer of the body size (#2511 by @filimonov)
- A CAS mount claim accepts only a strictly greater
writer_epoch: it no longer refreshes its own pair in the slot or replaces a newer incarnation of the same server, and a zero epoch counter is rejected (#2512 by @filimonov) - Fixes a rare data loss on CAS (content-addressed storage) disks: an insert that reused an existing blob at the moment GC deleted it could commit a reference to the deleted blob, and later reads of that part failed. The writer now uploads the blob again when its freshness marker is missing instead of reusing it. (#2552 by @filimonov)
system.cas_mountsgainsrenewal_in_progress,renewal_attemptsandlast_renewal_error, updated while a CAS mount lease renewal runs. (#2513 by @filimonov)- CAS observers (GC fencing, restart and remount reclaim) wait for the lease a mount holder declares in its slot, so a longer
cas_mount_lease_ttl_mson one server is never fenced early by a server with a shorter one; the setting is per server and mixed values are safe. (#2516 by @filimonov) - Fixes a rare data loss on CAS (content-addressed storage) disks backed by S3 stores with content-derived ETags (GCS is unaffected): a retried blob upload could bring back a blob that garbage collection had already scheduled for deletion, and the delayed deletion then removed a blob still in use. Blob uploads no longer resend the request that creates the object; CAS retries with a new upload instead. Under a store outage an insert may now fail with a retryable error after 8 attempts or once the 90-second deadline for starting attempts passes. (#2555 by @filimonov)
- A CAS mount lease renewal retries until the object store gives a definitive answer instead of giving up at a deadline. While the lease is too short to admit a write, writes pause and resume under the same epoch once a renewal is confirmed, instead of losing the mount and remounting. (#2517 by @filimonov)
- CAS:
cas_server_root_idmay not contain/. A server whose id contains/(for example from a{shard}/{replica}template) refuses to start the disk and must be recreated under a new id without/; data stored under the old id is not visible under the new one. An aborted transaction deletes its S3 staging object.SYSTEM CAS DROP POOL MEMBERand the owner refusals name the state or command that resolves them. (#2566 by @filimonov) - Hardening: certificate chains containing the compromised eMudhra intermediate CAs or the roots that issued them (
emSign Root TLS CA - G3,emSign ECC Root CA - G3) are rejected even if the trust store of the operating system still trusts them. The CA certificates embedded into the binary (used only when the system has none) are updated from the Chromium root store. There is no security issue in typical use cases. (ClickHouse#127318 by @alexey-milovidov via #2698) - Revert "Antalya 26.6 Backport of ClickHouse#126138 - Revert "Revert "Verify the server certificate hostname on outbound TLS connections""" (#2778 by @zvonand)
Bug Fixes (user-visible misbehavior in an official stable release)
- Fix partition and min/max pruning for Iceberg tables by
timestamp_nstype, fix writingDateTime(9)astimestamp_ns. (#2239 by @ianton-ru) - Antalya-26.6: Add 409 to the non-retriable HTTP Error list (#2330 by @subkanthi)
- Treat
LowCardinality(String)likeStringin empty-string comparison rewrite. (#2565 by @ianton-ru) - Creating a
disk(...)custom disk no longer blocks other disk creations and disk or storage policy lookups. Server start with several CASdisk(...)custom disks that wait out a stale mount lease now waits for them in parallel instead of one after another. Disks defined instorage_configuration.disksare unchanged. (#2573 by @filimonov) - Fix
NOT_FOUND_COLUMN_IN_BLOCKin the native Parquet V3 reader (regression from ClickHouse#93542) when aPREWHEREhad conjuncts sharing a common intermediate expression. (ClickHouse#107059 by @groeneai via #2623) - Fix a possible crash when querying the view over
Distributedwithenable_analyzer=0(ClickHouse#123431 by @mkmkme via #2652) - Fix a bug where using aliases and row policies with
enable_analyzer=0could error out (ClickHouse#123436 by @mkmkme via #2655) - Updated the bundled
brotlilib...
25.3.14.10003 Altinity Stable
25.3.14.10003 Altinity Stable as compared to v25.3.14.10002.altinitystable
Critical Bug Fixes
- Fixed CVE-2026-116366
Packages
Available for both AMD64 and Aarch64 from https://builds.altinity.cloud/#altinitystable as either .deb, .rpm, or .tgz
These binaries include additional changes whose source is temporarily withheld pending coordinated security disclosure. The public tag identifies the public source baseline and does not contain all changes used to build these binaries.
Docker images
Available for both AMD64 and Aarch64: altinity/clickhouse-server:25.3.14.10003.altinitystable
25.3.8.30002 Altinity FIPS
25.3.8.30002 Altinity FIPS as compared to v25.3.8.30001.altinityfips
Critical Bug Fixes
- Bump
brotlifrom v1.0.9 to v1.0.10; fix CVE-2026-111497 (#2752 by @mkmkme) - Hardening: certificate chains containing the compromised eMudhra intermediate CAs or the roots that issued them (
emSign Root TLS CA - G3,emSign ECC Root CA - G3) are rejected even if the trust store of the operating system still trusts them. The CA certificates embedded into the binary (used only when the system has none) are updated from the Chromium root store. There is no security issue in typical use cases. (ClickHouse#127318 by @alexey-milovidov via #2751) - Fixed CVE-2026-116366
Packages
Available for both AMD64 and Aarch64 from https://builds.altinity.cloud/#altinityfips as either .deb, .rpm, or .tgz
These binaries include additional changes whose source is temporarily withheld pending coordinated security disclosure. The public tag identifies the public source baseline and does not contain all changes used to build these binaries.
Docker images
Available for both AMD64 and Aarch64: altinity/clickhouse-server:25.3.8.30002.altinityfips
24.8.14.10551 Altinity Stable
24.8.14.10551 Altinity Stable as compared to v24.8.14.10550.altinitystable
Critical Bug Fixes
- Fixed CVE-2026-116366
Packages
Available for both AMD64 and Aarch64 from https://builds.altinity.cloud/#altinitystable as either .deb, .rpm, or .tgz
These binaries include additional changes whose source is temporarily withheld pending coordinated security disclosure. The public tag identifies the public source baseline and does not contain all changes used to build these binaries.
Docker images
Available for both AMD64 and Aarch64: altinity/clickhouse-server:24.8.14.10551.altinitystable
24.3.18.10428 Altinity Stable
24.3.18.10428 Altinity Stable as compared to v24.3.18.10427.altinitystable
Critical Bug Fixes
- Fixed CVE-2026-116366
Packages
Available for both AMD64 and Aarch64 from https://builds.altinity.cloud/#altinitystable as either .deb, .rpm, or .tgz
These binaries include additional changes whose source is temporarily withheld pending coordinated security disclosure. The public tag identifies the public source baseline and does not contain all changes used to build these binaries.
Docker images
Available for both AMD64 and Aarch64: altinity/clickhouse-server:24.3.18.10428.altinitystable
23.8.16.10044 Altinity Stable
23.8.16.10044 Altinity Stable as compared to v23.8.16.43.altinitystable
Critical Bug Fixes
- Bump
brotlifrom v1.0.9 to v1.0.10; fix CVE-2026-111497 (#1864 by @strtgbb) - Hardening: certificate chains containing the compromised eMudhra intermediate CAs or the roots that issued them (
emSign Root TLS CA - G3,emSign ECC Root CA - G3) are rejected even if the trust store of the operating system still trusts them. The CA certificates embedded into the binary (used only when the system has none) are updated from the Chromium root store. There is no security issue in typical use cases. (ClickHouse#127318 by @alexey-milovidov via #2727) - Fixed CVE-2026-116366
Packages
Available for both AMD64 and Aarch64 from https://builds.altinity.cloud/#altinitystable as either .deb, .rpm, or .tgz
These binaries include additional changes whose source is temporarily withheld pending coordinated security disclosure. The public tag identifies the public source baseline and does not contain all changes used to build these binaries.
Docker images
Available for both AMD64 and Aarch64: altinity/clickhouse-server:23.8.16.10044.altinitystable
26.3.60.20002 Altinity Antalya
26.3.60.20002 Altinity Antalya as compared to v26.3.60.20001.altinityantalya
Critical Bug Fixes
- Fixed CVE-2026-116366
Packages
Available for both AMD64 and Aarch64 from https://builds.altinity.cloud/#altinityantalya as either .deb, .rpm, or .tgz
These binaries include additional changes whose source is temporarily withheld pending coordinated security disclosure. The public tag identifies the public source baseline and does not contain all changes used to build these binaries.
Docker images
Available for both AMD64 and Aarch64: altinity/clickhouse-server:26.3.60.20002.altinityantalya
26.3.60.10002 Altinity Stable
26.3.60.10002 Altinity Stable as compared to v26.3.60.10001.altinitystable
Critical Bug Fixes
- Fixed CVE-2026-116366
Packages
Available for both AMD64 and Aarch64 from https://builds.altinity.cloud/#altinitystable as either .deb, .rpm, or .tgz
These binaries include additional changes whose source is temporarily withheld pending coordinated security disclosure. The public tag identifies the public source baseline and does not contain all changes used to build these binaries.
Docker images
Available for both AMD64 and Aarch64: altinity/clickhouse-server:26.3.60.10002.altinitystable
25.8.33.20004 Altinity Antalya
25.8.33.20004 Altinity Antalya as compared to v25.8.33.20003.altinityantalya
Critical Bug Fixes
- Fixed CVE-2026-116366
Packages
Available for both AMD64 and Aarch64 from https://builds.altinity.cloud/#altinityantalya as either .deb, .rpm, or .tgz
These binaries include additional changes whose source is temporarily withheld pending coordinated security disclosure. The public tag identifies the public source baseline and does not contain all changes used to build these binaries.
Docker images
Available for both AMD64 and Aarch64: altinity/clickhouse-server:25.8.33.20004.altinityantalya