Skip to content

Clarify the need of using database_engine: 'Shared' in the docs - #808

Merged
koletzilla merged 1 commit into
mainfrom
koletzilla/clickhouse-update-docs-claify-consistency
Nov 17, 2026
Merged

koletzilla merged 1 commit into
mainfrom
koletzilla/clickhouse-update-docs-claify-consistency

Conversation

@koletzilla

@koletzilla koletzilla commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Clarify that in Cloud, if you want read-after-write consistency, it's easier if you just set database_engine: 'Shared' as it will include the select_sequential_consistency in more places


Note

Low Risk
Documentation-only clarification with no code or configuration behavior changes.

Overview
Updates the dbt–ClickHouse features and configurations guide so ClickHouse Cloud users are steered toward database_engine: Shared for read-after-write consistency instead of only setting select_sequential_consistency via custom_settings.

The database_engine profile example comment now points readers to the read-after-write consistency section and calls out Shared on Cloud. That section was rewritten to recommend database_engine: Shared (case-sensitive) because the adapter applies select_sequential_consistency: 1 on every connection, including internal queries that custom_settings does not cover.

Reviewed by Cursor Bugbot for commit a16a09c. Bugbot is set up for automated code reviews on this repo. Configure here.

@koletzilla
koletzilla requested a review from canbekley November 17, 2026 12:34

@canbekley canbekley left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@koletzilla
koletzilla merged commit f229423 into main Nov 17, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants