docs: add DuckLake guide#448
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Greptile SummaryAdds a thorough DuckLake guide (install, secrets, single/multi-machine attach, inserts, time travel, schema evolution, read-only mounts) alongside the existing DuckDB quickstart, with a matching architecture diagram component. Two P1 issues need attention before merging:
Confidence Score: 3/5Two P1 issues should be resolved before merging: a truncated bullet in the new guide and a missing link fix that was described but not applied. Two separate P1 findings (truncated content and an unapplied fix advertised in the PR description) pull the score below the P1 ceiling of 4. docs/quickstarts/ducklake.mdx (truncated bullet) and docs/quickstarts/duckdb.mdx (stale link not fixed) Important Files Changed
|
| "fontSize": 14, | ||
| "strokeColor": "#8fa3b0" | ||
| }, | ||
| { | ||
| "type": "text", | ||
| "id": "annotation2", | ||
| "x": 40, | ||
| "y": 492, | ||
| "text": "file in Tigris and a new snapshot row in the catalog.", | ||
| "fontSize": 14, | ||
| "strokeColor": "#8fa3b0" | ||
| } | ||
| ] |
There was a problem hiding this comment.
Diagram annotation restates body text
The two annotation text nodes below the diagram repeat the same sentence that already appears in the guide body ("each write produces a new Parquet file in your bucket and a new snapshot row in the catalog"). Per the team's rule on redundant explanatory notes, consider removing or replacing these annotations with information the diagram itself doesn't already convey (e.g. the arrow labels "metadata" and "data" already communicate the split).
Rule Used: Avoid adding explanatory notes that simply restate... (source)
Learned From
tigrisdata/tigris-os-docs#265
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Adds a guide for running a DuckLake lakehouse on Tigris. Sits next
to the DuckDB quickstart under Guides → Integrations → Data &
Analytics.
Covers install, the S3 secret, attaching with either local DuckDB
or Postgres metadata, reads and writes, time travel, schema
evolution, and read-only mounts. Each section opens with a short
explanation in plain English; the SQL underneath is copy-pasteable.
Includes a small architecture diagram showing the catalog/data
split, in the same style as the existing diagrams.
Also fixes a stale link in the DuckDB quickstart
(iam/create-access-key → iam/manage-access-key) and points it at
the new guide instead of GitHub.