TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
DuckDB’s DuckLake extension lets DuckDB read and write DuckLake, an open lakehouse format that stores metadata in a catalog database and data in Parquet files. The project documentation shows SQL workflows for table changes, time travel, schema evolution and change data feeds; it does not specify a release date or broader deployment claims.
DuckDB’s DuckLake extension enables the database engine to read and write DuckLake, an open lakehouse format that stores metadata in a catalog database and table data in Parquet files. The project’s GitHub documentation describes SQL workflows including updates, time travel, schema changes and change data feeds, giving users a way to work with the format directly through DuckDB.
The extension’s documented setup uses DuckDB’s INSTALL ducklake command. Users can then attach a DuckLake database using DuckDB’s ATTACH syntax, identifying a catalog and, in the example, a directory for Parquet data files. Once attached, the guide shows creating tables, inserting rows and querying them with standard SQL. This keeps interaction with the lakehouse within DuckDB’s usual SQL interface rather than requiring a separate format-specific query language.
The examples also demonstrate UPDATE operations and querying an earlier table version with DuckLake’s version argument. A user can add a column with ALTER TABLE, while the documented change-feed function returns records with snapshot IDs, row identifiers and change types. These are capabilities shown in the project documentation; the examples do not establish performance results or describe production-scale behavior.
The repository provides installation instructions for the extension and says a latest development version can be installed from DuckDB’s core_nightly channel. It also includes build and test guidance, including configurations using PostgreSQL or SQLite as catalog databases. The project says its active development branch is main and directs contributions there, indicating ongoing development rather than a fixed, fully described commercial release.
SQL Access to Lakehouse Tables
DuckLake’s approach separates catalog metadata from Parquet data files, while the extension gives DuckDB a direct route to both read and write the format. For analysts and developers already using DuckDB, the documented SQL interface could make it easier to query and modify lakehouse tables without changing their basic interaction pattern. The importance is practical: common table operations and version-aware queries appear in the same workflow.
Time travel and change feeds can also support tasks such as reviewing prior table states or examining recorded changes. The documentation demonstrates how those features are called, but it does not quantify their reliability, speed, cost or suitability for particular workloads. Readers should treat the material as a description of available project functionality, not independent evidence of performance or a guarantee of compatibility across systems.
As an affiliate, we earn on qualifying purchases.
How DuckLake Stores Data
DuckLake is described by its project as an open format built on SQL and Parquet. Rather than putting its metadata in the data files themselves, it stores metadata in a catalog database and table data in Parquet files. The DuckDB extension is the connector that lets DuckDB operate on this arrangement.
The project documentation presents both a DuckDB database file and other catalog options in its test instructions. It lists PostgreSQL and SQLite configurations, although those testing examples alone do not fully describe supported deployment setups or guarantees. The repository also gives developers instructions for building the extension against the DuckDB version specified for its continuous-integration builds.
“DuckLake is an open Lakehouse format that is built on SQL and Parquet.”
— DuckLake project documentation
As an affiliate, we earn on qualifying purchases.
Release and Compatibility Details
The supplied project material does not give a release date, version number, stability designation or support timetable for the extension. It also does not report independent testing, performance measurements, or comparisons with other lakehouse formats. While the repository includes tests for multiple catalog configurations and deletion vectors, those entries do not on their own establish the complete scope of supported features or their production readiness.
It is also unclear from this documentation how the project intends to manage compatibility across DuckDB versions, what operational requirements apply to different catalogs, or what limitations users may encounter with larger workloads. The examples establish that certain operations are documented, but they do not answer those deployment questions.
As an affiliate, we earn on qualifying purchases.
Development and Testing Continue
The repository says the extension’s active development branch is main and that contributions should target that branch. It provides commands for running the DuckLake test suite, selected tests, DuckDB core tests with DuckLake as a storage backend, and tests configured for SQLite or PostgreSQL catalogs. These instructions point users and contributors to the project’s current code and test process.
For users tracking the extension, the next concrete information to watch for is updated project documentation, tagged releases or stated compatibility guidance. The material supplied here does not announce a scheduled release or a specific future milestone, so those details remain unconfirmed.
lakehouse data management software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is the DuckDB DuckLake extension?
It is a DuckDB extension that the project says can read and write DuckLake data. DuckLake stores metadata in a catalog database and table data in Parquet files.
What SQL operations are shown?
The project examples show creating and querying tables, inserting and updating rows, adding a column, querying an earlier version and calling a change data feed function.
How do users install it?
The repository documents installation with DuckDB’s INSTALL ducklake command. It separately provides an instruction for installing a development version from the core_nightly channel.
Is the extension described as production-ready?
The supplied documentation does not state a stability level or make a production-readiness claim. It includes development, build and testing instructions, but release status and workload limitations are not specified.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
