Migration: Cloud data catalog integration quickstart#315
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
5 tasks
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
Ports clickhouse/clickhouse-docs#6449 — adds a ClickHouse Cloud UI walkthrough for linking open table format catalogs and refreshes the Cloud data catalogs support matrix.
Changes
integrations/data-catalogs.mdx(slug/integrations/data-catalogs) — step-by-step Cloud UI quickstart for AWS Glue, Unity Catalog (Iceberg/Delta), REST catalog, Microsoft OneLake, Polaris, and BigLake Metastore.products/cloud/features/data-catalogs.mdx— support matrix rebuilt into Cloud vs Core columns, links to the new quickstart with?catalog=…#…anchors, adds a BigLake row and splits Unity Catalog into Iceberg/Delta rows.images/integrations/data-catalogs/(catalog-flyout-select.png,catalog-sql-query.png,catalog-tables-browser.png,linked-catalogs-table.png) and refreshedimages/cloud/features/data-catalogs-ui.png.docs.json— registeredintegrations/data-catalogsunder the Integrations tab's Ecosystem menu.Migration notes / ambiguity
<Tabs queryString="catalog">so that?catalog=aws-gluedeep-links to a specific tab. Mintlify's<Tabs>doesn't support querystring-driven tab selection, so tabs default to the first one on load. The?catalog=…links in the Cloud page were preserved as-is (they'll still route to/integrations/data-catalogsand the anchor#add-your-catalog-connectionstill scrolls), but the specific tab will not be pre-selected. Worth revisiting if we need parity.<VerticalStepper>was mapped to Mintlify's<Steps>/<Step>. Per-step{#anchor}slugs were preserved as inline<a id="…"></a>tags so any external links to#open-flyout,#add-your-catalog-connection,#save-connection,#view-tables,#run-a-querycontinue to resolve.:::noteadmonitions converted to Mintlify<Note>.borderprop dropped — the MintlifyImagesnippet doesn't expose it.i18n/en/code.json,sidebars.js,src/theme/Navbar/Content/MenuData.js— Docusaurus-only files with no Mintlify equivalent.mint validatepassed.mint broken-linkstimed out on the full site scan and wasn't re-run; all new internal links use slugs that already exist in the slug map.Context
Upstream: ClickHouse/clickhouse-docs#6449 (commit
266d32d).