Skip to content

Backport #94000 to 25.11: Fix join with StorageJoin with USING clause#94592

Merged
novikd merged 2 commits into25.11from
backport/25.11/94000
Jan 21, 2026
Merged

Backport #94000 to 25.11: Fix join with StorageJoin with USING clause#94592
novikd merged 2 commits into25.11from
backport/25.11/94000

Conversation

@robot-ch-test-poll
Copy link
Copy Markdown
Contributor

Original pull-request #94000
Cherry-pick pull-request #94591

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

@robot-ch-test-poll robot-ch-test-poll added pr-backport Changes, backported to release branch. Do not use manually - automated use only! pr-critical-bugfix labels Jan 19, 2026
@clickhouse-gh
Copy link
Copy Markdown
Contributor

clickhouse-gh bot commented Jan 19, 2026

Workflow [BackportPR], commit [2ab0ca6]

Summary:

job_name test_name status info comment
Integration tests (amd_asan, db disk, old analyzer, 2/6) failure
test_throttling/test.py::test_read_throttling[user_remote_throttling] FAIL cidb

@novikd novikd merged commit 6c9708c into 25.11 Jan 21, 2026
31 of 34 checks passed
@novikd novikd deleted the backport/25.11/94000 branch January 21, 2026 14:23
@clickhouse-gh clickhouse-gh bot added the ready-for-backport PR is eligible for backporting (merged 7+ days ago, not reverted) label Mar 27, 2026
@maxknv maxknv removed the ready-for-backport PR is eligible for backporting (merged 7+ days ago, not reverted) label Mar 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-backport Changes, backported to release branch. Do not use manually - automated use only! pr-critical-bugfix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants