Visitar URL original
Revert #129096: hardcode the CI DB read URL again by maxknv · Pull Request #131283 · ClickHouse/ClickHouse · GitHub
Skip to content

Revert #129096: hardcode the CI DB read URL again - #131283

Open
maxknv wants to merge 1 commit into
masterfrom
revert-cidb-read-url-from-ssm
Open

maxknv wants to merge 1 commit into
masterfrom
revert-cidb-read-url-from-ssm

Conversation

@maxknv

@maxknv maxknv commented Nov 13, 2026 •

Copy link
Copy Markdown
Member

Reverts #129096 (#129096).

#129096 made the CI DB read path resolve its URL from the SSM connection secret via CIDB.get_read_url. That secret holds the write cluster URL, so reads started pointing at the write endpoint. This is a regression: CI_DB_READ_URL was introduced precisely to use a different URL for reads than for writes.

This PR restores the hardcoded Settings.CI_DB_READ_URL and the per-script read-URL literals, now pointing at the new staging read host instead of play.clickhouse.com.

The stored value is the host root. Link builders append /play themselves (cidb.py, build_perf_query_history_link), so the setting must hold the root; POST query endpoints append /?.... On the new host, /play serves only the web UI while / serves the HTTP query API, so a single .../play value would break both the generated links and the query POSTs. The root value yields the correct .../play?user=play&run=1#<query> links and working query POSTs.

Hardcoding is a drawback we accept for now; an SSM parameter for the read URL with a hardcoded fallback can replace it later.

Related: #129096

Changelog category (leave one):

  • CI Fix or Improvement (changelog entry is not required)

Workflow [PR]
Sync PR [sync-upstream/pr/131283]

PR #129096 made the CI DB read path resolve its URL from the SSM
connection secret via `CIDB.get_read_url`. That secret holds the write
cluster URL, so reads started pointing at the write endpoint - a
regression, since `CI_DB_READ_URL` exists precisely to use a different
URL for reads than for writes.

This reverts #129096 and restores the hardcoded `Settings.CI_DB_READ_URL`
and the per-script read-URL literals, now pointing at the new staging
read host instead of `play.clickhouse.com`.

The stored value is the host root. Link builders append `/play`
themselves (`cidb.py`, `build_perf_query_history_link`), so the setting
must hold the root; POST query endpoints append `/?...`. On the new host
`/play` serves only the web UI while `/` serves the HTTP query API, so a
single `.../play` value would break both the generated links and the
query POSTs.

Hardcoding is a drawback we accept for now; an SSM parameter for the read
URL with a hardcoded fallback can replace it later.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@clickhouse-gh

clickhouse-gh Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Workflow [PR], commit [5857aec]


AI Review

Summary

The PR restores a dedicated CI database read URL and points readers and history links at the staging endpoint. Request changes: the restored documentation examples still fail before executing their SQL because the shared client sends a setting forbidden by the read-only profile.

Findings

⚠️ Majors

  • .claude/docs/relevant_tests.md:51: Both restored CIDB.query examples, including the freshness example at line 320, fail with play. CIDB._post_with_retries always sends queue_max_wait_ms, and the endpoint rejects it with HTTP 500 / code 164: Cannot modify 'queue_max_wait_ms' setting in readonly mode. (READONLY). A live SELECT 1 through the actual client reproduces the failure even with log_level=""; the previous public read host has the same incompatibility. Use a read-only-compatible query path in the examples, or make read-only requests omit the forbidden setting.
Final Verdict

⚠️ Request changes — Make the restored read examples executable with play, verified by a successful SELECT 1 through their documented client path.

@clickhouse-gh clickhouse-gh Bot added the pr-ci label Nov 13, 2026
@clickhouse-gh
clickhouse-gh Bot requested a review from leshikus November 13, 2026 12:26
Comment thread .claude/docs/relevant_tests.md Resolved

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant