Skip to content

Conversation

jgao54
Copy link
Contributor

@jgao54 jgao54 commented Sep 8, 2025

Summary

  • Update quick start documentation to provide example for incremental materialized view
  • Add a FAQ section
  • _full_document -> doc
  • private preview -> beta

@CLAassistant
Copy link

CLAassistant commented Sep 8, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link

vercel bot commented Sep 8, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
clickhouse-docs Ready Ready Preview Comment Sep 9, 2025 5:41pm
3 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
clickhouse-docs-jp Ignored Ignored Sep 9, 2025 5:41pm
clickhouse-docs-ru Ignored Ignored Preview Sep 9, 2025 5:41pm
clickhouse-docs-zh Ignored Ignored Preview Sep 9, 2025 5:41pm

@jgao54 jgao54 marked this pull request as ready for review September 8, 2025 22:09
@jgao54 jgao54 requested review from a team as code owners September 8, 2025 22:09
@jgao54 jgao54 requested a review from iskakaushik September 8, 2025 22:10
@@ -266,11 +266,11 @@ LIMIT 10;

### Refreshable materialized view {#refreshable-materialized-view}

You can also create [Refreshable Materialized Views](https://clickhouse.com/docs/materialized-view/refreshable-materialized-view), which enable you to schedule query execution for deduplicating rows and storing the results in a flattened destination table. With each scheduled refresh, the destination table is replaced with the latest query results.
If your table size is small, you can create [Refreshable Materialized Views](https://clickhouse.com/docs/materialized-view/refreshable-materialized-view), which enable you to schedule query execution for deduplicating rows and storing the results in a flattened destination table. With each scheduled refresh, the destination table is replaced with the latest query results.
Copy link
Contributor

Choose a reason for hiding this comment

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

If I was the user of this documentation, I would ask myself the question "what does small mean"? 1MB? 1GB? 1TB?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch. going to remove If your table size is small,, I think table size has less impact here than update frequency, and scaling depends on frequency of refresh.

Copy link
Contributor

@whites11 whites11 left a comment

Choose a reason for hiding this comment

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

A few comments/suggestions but overall LGTM

@jgao54 jgao54 merged commit 0dc1521 into main Sep 9, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants