Docs: Cloud data catalog integration quickstart#6449
Conversation
Introduce a step-by-step UI guide with per-catalog deep links and update the Cloud integrations page with a clearer support matrix. Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit f7a2f60. Configure here.
Show the public beta badge on the Cloud quickstart and integrations landing page again. Co-authored-by: Cursor <cursoragent@cursor.com>
Remove extra consecutive blank lines so CI markdown checks pass. Co-authored-by: Cursor <cursoragent@cursor.com>
Keep the Data sources UI image on the manage landing page and add it to the Cloud integration quickstart intro for context. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…into docs/data-catalog-cloud-quickstart
Adds integrations/data-catalogs/index to the Data sources sidebar category, next to the object-storage entries. The page was created without a sidebar entry, which failed the floating-pages build check on DocsCheck and Vercel. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- /materialized-view -> /materialized-views (index page slug) - /use-cases/data-lake/guides/accelerating-analytics -> /use-cases/data-lake/getting-started/accelerating-analytics Both were failing the Docusaurus broken-links check on the Vercel build. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
| 'integrations/data-sources/cassandra', | ||
| 'integrations/data-ingestion/gcs/index', | ||
| 'integrations/data-ingestion/s3-minio', | ||
| 'integrations/data-catalogs/index', |
There was a problem hiding this comment.
Added this sidebar so that the preview build would pass, but I'm not convinced with this placement. Also the label as it is right now in the sidebar is "Connect a data catalog", perhaps it can just be Data catalog.
| # Connect a data catalog in ClickHouse Cloud | ||
|
|
||
| :::info | ||
| Data catalog integrations in ClickHouse Cloud are in public beta. |
There was a problem hiding this comment.
I don't think this is needed because of the BetaBadge up top.
| Data catalog integrations in ClickHouse Cloud are in public beta. | ||
| ::: | ||
|
|
||
| Connect ClickHouse Cloud to your data catalogs to access your open table format tables. You can set up connections in the **Data sources** UI. For setup via SQL, use the `[DataLakeCatalog](/engines/database-engines/datalakecatalog)` database engine in your SQL editor of choice. |
There was a problem hiding this comment.
| Connect ClickHouse Cloud to your data catalogs to access your open table format tables. You can set up connections in the **Data sources** UI. For setup via SQL, use the `[DataLakeCatalog](/engines/database-engines/datalakecatalog)` database engine in your SQL editor of choice. | |
| Connect ClickHouse Cloud to your data catalogs to access your open table format tables. You can set up connections in the **Data sources** UI. For setup via SQL, use the [`DataLakeCatalog`](/engines/database-engines/datalakecatalog) database engine in your SQL editor of choice. |
Fixing the backticks here so that the link renders properly.
|
|
||
| | Name | Open table format | Auth method | Cloud | Core | Version | | ||
| | ----------------- | ----------------- | -------------------------------------- | ---------------------------------------------------------- | ------------------------------------------------ | ------- | | ||
| | AWS Glue Catalog | Iceberg | IAM role (26.2+), Access keys | [Guide](/integrations/data-catalogs?catalog=aws-glue) | [Guide](/use-cases/data-lake/glue-catalog) | 25.10+ | |
There was a problem hiding this comment.
What is the intention of these query string params in these links (?catalog=aws-glue). As of now, every link lands at the top of the page.
| 1. Fill in the connection parameters and **Database name** for your catalog type. The **Database name** is the ClickHouse database that exposes your catalog tables in the SQL console. | ||
| Select your catalog below for field-level guidance and prerequisites. | ||
|
|
||
| [AWS Glue Catalog](/use-cases/data-lake/glue-catalog) exposes [Iceberg](/engines/table-engines/integrations/iceberg) tables registered in the Glue Data Catalog. |
There was a problem hiding this comment.
I'd suggest for each of these Catalog sections that we give them a seperate header or create a tabbed section with each catalog.

Summary
/integrations/data-catalogswith a ClickHouse Cloud UI walkthrough for linking open table format catalogs, including screenshots and per-catalog anchor links.Test plan
/integrations/data-catalogs?catalog=...) scroll or highlight the intended sectionsstatic/images/integrations/data-catalogs//cloud/features/integrations/data-catalogslinks and table formattingMade with Cursor