646 signals · 904 observation events
ClickHouse® is a real-time analytics database management system
v26.7.3.19-stableOpen the original release notes for details.
Original release notes ↗Prereleases and milestones indicate public plans; they are not delivery commitments.
### Changelog category (leave one): - Bug Fix (user-visible misbehavior in an official stable release) ### Changelog entry (a [user-readable short description](https://github.com/ClickHouse/ClickHouse/blob/master/docs/changelog_entry_guidelines.md) of the changes that goes into CHANGELOG.md): Accept trailing commas in PromQL grouping label lists. ### Descrip
Related: https://github.com/ClickHouse/ClickHouse/pull/55656 `IExecutableFunction::canThrow` decides whether the rows that a query does not reference have to be removed from `ColumnReplicated` arguments before a function is executed. It was derived from `isSuitableForShortCircuitArgumentsExecution`, with a `TODO` in `IFunctionAdaptors.h` asking for a dedicat
### Changelog category (leave one): - Bug Fix (user-visible misbehavior in an official stable release) ### Changelog entry (a [user-readable short description](https://github.com/ClickHouse/ClickHouse/blob/master/docs/changelog_entry_guidelines.md) of the changes that goes into CHANGELOG.md): Support quoted metric and label names in PromQL selectors. ### Des
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/110283 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/110283 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/110283 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
### Changelog category (leave one): - Improvement ### Changelog entry (a [user-readable short description](https://github.com/ClickHouse/ClickHouse/blob/master/docs/changelog_entry_guidelines.md) of the changes that goes into CHANGELOG.md): PromQL: support `@ start()` and `@ end()` timestamp modifiers. ### Summary PromQL allows `start()` and `end()` as speci
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/113534 Cherry-pick pull-request https://github.com/ClickHouse/ClickHouse/pull/114423 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target bran
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/112921 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target branch, otherwise just close it. ### The PR source The PR is created in the [CI jo
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/112498 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/112498 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/112498 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/112498 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target branch, otherwise just close it. ### The PR source The PR is created in the [CI jo
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/112498 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target branch, otherwise just close it. ### The PR source The PR is created in the [CI jo
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/107028 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/107028 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/107028 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target branch, otherwise just close it. ### The PR source The PR is created in the [CI jo
Closes: https://github.com/ClickHouse/ClickHouse/issues/44930 Related: https://github.com/ClickHouse/ClickHouse/pull/48560 `information_schema.columns` decided nullability by matching the printed type name (`type LIKE 'Nullable(%)'`), so a `LowCardinality(Nullable(T))` column — which accepts `NULL` — was reported as `is_nullable = 0`, and MySQL-compatible cl
When loading a part's statistics, the part currently loads statistics for every column via `getEstimates`, even when only a few columns are needed. On wide tables this performs a lot of pointless deserialization. Related: https://github.com/ClickHouse/ClickHouse/pull/104691 This change makes per-part statistics load lazily, only for the requested columns: -
Related: https://github.com/ClickHouse/ClickHouse/pull/113376 Related: https://github.com/ClickHouse/ClickHouse/pull/110757 I first tried to fix the edge cases between `JSONAllValues` and the text index. I kept finding more cases where the index could return an incorrect result. I therefore needed to disable more useful index paths to keep queries correct. T
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/112573 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target branch, otherwise just close it. ### The PR source The PR is created in the [CI jo
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/112573 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target branch, otherwise just close it. ### The PR source The PR is created in the [CI jo
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/112573 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target branch, otherwise just close it. ### The PR source The PR is created in the [CI jo
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/94748 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target branch, otherwise just close it. ### The PR source The PR is created in the [CI job
Backport of https://github.com/ClickHouse/ClickHouse/pull/112217 to `26.7`. Related: https://github.com/ClickHouse/ClickHouse/pull/112217 Related: https://github.com/ClickHouse/ClickHouse/pull/114478 ### Changelog category (leave one): - CI Fix or Improvement (changelog entry is not required) ### Description `test_backup_restore_on_cluster/test_cancel_backup
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/113742 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/113742 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/113742 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/113742 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target branch, otherwise just close it. ### The PR source The PR is created in the [CI jo
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/113742 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target branch, otherwise just close it. ### The PR source The PR is created in the [CI jo
<!-- Linked issues and pull requests. Use full GitHub URLs, one relationship per line; delete the lines you don't need. Closes: https://github.com/ClickHouse/ClickHouse/issues/NNNNN (auto-closes the issue when this PR is merged into the default branch) Related: https://github.com/ClickHouse/ClickHouse/pull/NNNNN --> ### Changelog category (leave one): - Not
Closes: https://github.com/ClickHouse/ClickHouse/issues/111692 Implement `[NOT] [I]LIKE 'pattern'` for all `SHOW` statements that list access entities: - `SHOW USERS` - `SHOW ROLES` / `SHOW CURRENT ROLES` / `SHOW ENABLED ROLES` - `SHOW SETTINGS PROFILES` - `SHOW QUOTAS` - `SHOW ROW POLICIES` - `SHOW MASKING POLICIES` This allows filtering access entities by
## Summary - move the ODBC driver guide into a group-backed folder under `concepts/features/interfaces` - remove the duplicate ODBC connector page and its navigation entry - redirect the retired connector URL and its legacy alias directly to the ODBC table-engine reference - update remaining English documentation links to bypass the redirect ## Why The retir
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/114188 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/114188 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/114188 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/114188 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/114188 ## Do not merge this PR manually This pull-request is a first step of an automated backporting. It contains changes similar to calling `git cherry-pick` locally. If you intend to continue backporting the changes, then resolve all conflicts if any. Otherwise, if you do not want to back
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/113450 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target branch, otherwise just close it. ### The PR source The PR is created in the [CI jo
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/113450 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target branch, otherwise just close it. ### The PR source The PR is created in the [CI jo
Original pull-request https://github.com/ClickHouse/ClickHouse/pull/113450 This pull-request is a last step of an automated backporting. Treat it as a standard pull-request: look at the checks and resolve conflicts. Merge it only if you intend to backport changes to the target branch, otherwise just close it. ### The PR source The PR is created in the [CI jo
<!-- Related: https://github.com/ClickHouse/ClickHouse/pull/113051 --> Continue removing `DB::Field` from constant handling by promoting the owning single-constant type to a shared primitive with `Field`-free value accessors. ### What - **Move `ConstantValue` from `Analyzer/` to `Core/`.** It bundles `{size-1 ColumnConst, DataTypePtr}`. It carries a `DataTyp
Closes: https://github.com/ClickHouse/ClickHouse/issues/114616 When a file-backed table (`File`, and the same path for object storage) has a `DEFAULT` column that is not present in the data file, a row policy or `PREWHERE` could prune the inputs of that default expression before `AddingDefaultsTransform` ran. That led to `UNKNOWN_IDENTIFIER` on current maste
<!-- Related: https://github.com/ClickHouse/ClickHouse/pull/114472 --> Makes the release-creation steps self-gating so an idempotent operation decides for itself whether there is work to do, instead of the orchestrator gating on `is_recovery` / `is_late_recovery` flags with fail-closed `True` defaults. - `ci/jobs/scripts/create_release.py`: `push_release_tag
`TRUNCATE TABLE` held the table's DDL guard while removing data, and truncate can wait for running merges or for other replicas to process `DROP_RANGE`. Any DDL on that name — including background threads that need it — was blocked for that whole time. Release the guard before `IStorage::truncate` for databases with UUIDs, matching `ALTER TABLE ... DROP PART
Assisted-by: Claude Sonnet 4.5 via GitHub Copilot ### Changelog category (leave one): - Bug Fix (user-visible misbehavior in an official stable release) ### Changelog entry (a [user-readable short description](https://github.com/ClickHouse/ClickHouse/blob/master/docs/changelog_entry_guidelines.md) of the changes that goes into CHANGELOG.md): Fix invalid resu