docs: document DuckLake as a DuckDB connection type#693
Open
sdolidze wants to merge 1 commit into
Open
Conversation
Restructure the DuckDB section to cover both MotherDuck and DuckLake modes. Adds catalog backend (Postgres / SQLite / DuckDB file) and data path backend (S3 / GCS / Azure / local) field descriptions, plus dbt profile examples for the two most common DuckLake shapes. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Contributor
🤖 Documentation BotStatus🔗 Broken Links (Manual Fix Required)Click to view details |
Contributor
|
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
1 participant
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
Documents DuckLake as a second connection type for DuckDB project connections, alongside the existing MotherDuck mode. The setup tile is renamed from "MotherDuck" to "DuckDB", and the connection type is chosen from a MotherDuck / DuckLake toggle inside the form.
DuckLake combines any supported catalog backend (PostgreSQL, SQLite, DuckDB file) with any supported data path (S3-compatible, GCS, Azure Blob Storage, or local filesystem) to query Parquet data through DuckDB.
Upstream code change: lightdash/lightdash#23446.
Changes
### DuckDBsection into a shared intro plus#### MotherDuckand#### DuckLakesubsections. MotherDuck content is unchanged.profiles.ymlexamples: PostgreSQL + S3 (three-secret pattern with theducklake:attach form) and SQLite + local data path (inlineducklake:sqlite:attach form).Layout
Context
This supersedes #692 (the earlier auto-generated version), which labelled the tile MotherDuck / DuckLake. The actual frontend change renames the tile to DuckDB and moves the mode toggle inside the form, so this version matches the shipped UI.
Test plan
mintlify devand confirm the### DuckDBsection renders with the two subsections and both fenced YAML examples.#duckdb.🤖 Generated with Claude Code