Repository navigation
Stable 24.8 Backport of #123436 - Fix ALIAS row policies on legacy distributed reads - #2479
Conversation
…-distributed-26.8 Fix `ALIAS` row policies on legacy distributed reads
|
This is an automated comment for commit 8cb93db with description of existing statuses. It's updated for the latest CI running ❌ Click here to open a full report in a separate page
Successful checks
|
CI triage — @mkmkmeVerdict: 0 PR-caused failures. All red checks are flaky, infra, or base-image dependency issues. This PR touches only Not PR-caused1. Stateless tests (asan) [1/2] — flaky This is a mutation profile-events test — it does not exercise row policies or 2. Regression release lightweight_delete — flaky (timing/concurrency)
Neither involves row policies/ 3. Regression S3 (azure, 1) & TieredStorage (s3gcs) — infra abort 4. Grype Scan (server, -alpine) & GrypeScan (keeper) — base-image CVE 5. FinishCheck / "CI running" — aggregate gates, red only because of the above. Health checkFunctionally this backport is clean: it modifies only Recommendation: re-run the stateless-asan, lightweight_delete, s3_azure_1, and tiered_storage_s3gcs jobs; handle the grype base-image CVE separately. Nothing to fix in this PR. — @blau-ai (automated triage; I can't build/run ClickHouse, so this is evidence-based from the CI reports) |
Fix
ALIASrow policies on legacy distributed readsChangelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Fix a bug where using aliases and row policies with
enable_analyzer=0could error out (ClickHouse#123436 by @mkmkme)Documentation entry for user-facing changes
...
CI/CD Options
Exclude tests:
Regression jobs to run: