Skip to content

Wire DuckLake extension into build and ATTACH hint - #1002

Merged
adsharma merged 2 commits into
LadybugDB:mainfrom
adsharma:feature/ducklake-pushdown
Sep 20, 2026
Merged

adsharma merged 2 commits into
LadybugDB:mainfrom
adsharma:feature/ducklake-pushdown

Conversation

@adsharma

Copy link
Copy Markdown
Contributor

Wires up the new DuckLake storage extension (LadybugDB/extensions#87):

  • extensions submodule @ feature/ducklake-pushdown (new ducklake ext: DBTYPE DUCKLAKE with SQL pushdown via the embedded-DuckDB path, no optimizer changes needed)
  • Makefile EXTENSION_LIST += ducklake
  • ATTACH error hint suggests the ducklake extension too

Verification: ducklake.DuckLakeScan + ducklake.DuckLakeJoinPushdown e2e cases pass; EXPLAIN confirms join pushdown; the one unrelated e2e failure (duckdb.AttachDBWithoutLoadingExtension) reproduces on a clean tree.

- Resolve the node-table ID column from the bound catalog entry's
  primary key instead of assuming it is the first foreign column;
  fall back to an `id`-named column before ordinal position.
- Simplify the src/dst endpoint predicate into an isEndpointColumn
  helper shared (by convention) with DuckDBCatalog.
- Document the all-or-nothing endpoint fallback and the unqualified
  table-name fallback trade-off; extract quote-stripping helpers.
- extensions submodule @ feature/ducklake-pushdown (new ducklake ext)
- Makefile EXTENSION_LIST += ducklake
- ATTACH error hint suggests the ducklake extension too
@adsharma
adsharma merged commit 0a90045 into LadybugDB:main Sep 20, 2026
4 checks passed
@adsharma
adsharma deleted the feature/ducklake-pushdown branch September 20, 2026 04:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant