Improve docs from user feedback: clarify direct vs. indirect source refs in MV JOINs - #121284
Open
mintlify[bot] wants to merge 1 commit into
Open
mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
|
Workflow [PR], commit [23f9b70] Summary: ❌
|
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Clarifies how ClickHouse substitutes the source table inside an incremental materialized view's SELECT when it fires, so readers can predict mvw1 vs. mvw2 behavior without re-reading the section.
Changes
Feedback basis
Recent contextual feedback on this page reported that the "Using source table in filters and joins" section was hard to understand, specifically around direct vs. indirect references to the source table, and suggested comparing the two example views side by side. The update adds that comparison and puts the substitution rule up front.
Workflow [PR]
Sync PR [sync-upstream/pr/121284]