TL;DR
Get business pricing on networking and server gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
DuckDB’s DuckLake extension lets DuckDB attach to DuckLake databases and read or write their tables through SQL. The project describes DuckLake as an open lakehouse format that stores metadata in a catalog database and data in Parquet files; the supplied documentation does not establish a release date, adoption figures or production-readiness claims.
DuckDB’s DuckLake extension allows users to attach to a DuckLake database and create, modify and query tables with standard SQL, connecting catalog-stored metadata with data held in Parquet files. The project’s GitHub documentation presents features including updates, schema changes, version-based time travel and change-data queries, but does not specify a release date or describe the extension’s maturity.
DuckLake is described in the repository as an open lakehouse format built on SQL and Parquet. Its metadata is stored in a catalog database, while table data is kept in Parquet files. The extension links that format to DuckDB, so users can attach a DuckLake database and work with its tables through familiar SQL statements rather than a separate query interface.
The usage example in the documentation attaches a DuckLake database with a metadata file named metadata.ducklake and sets a separate directory for Parquet data. It then creates a table, inserts two rows and queries them. The same example updates a row, adds a column and retrieves an earlier table version, illustrating several operations exposed through the SQL interface.
The repository also documents a change-data query that returns snapshot IDs, row IDs, change types and row values. For installation, it lists DuckDB’s INSTALL ducklake; command and a separate command for installing the latest development version from the core_nightly repository. These are instructions in the project documentation, not evidence of a particular packaged release or support commitment.
SQL Access to Parquet Lakehouse Tables
For teams already using DuckDB, the extension offers a way to work with DuckLake-managed data through standard SQL. The separation of catalog metadata from Parquet data also makes the format’s storage arrangement explicit: the catalog records information needed to manage tables, while the table data resides in files.
The documented operations matter for more than basic querying. Version-based reads can let users inspect an earlier state, while change-data queries expose recorded row changes over a selected range. Schema modification is also included in the example. Together, these capabilities indicate that DuckLake is intended to support managed table workflows, not only one-time reads of Parquet files.
That description should not be read as proof of compatibility with every catalog, storage service or analytics engine. The supplied material does not give performance comparisons, availability guarantees or adoption data. For readers evaluating the format, the concrete news is the documented DuckDB interface and feature set—not a verified claim that DuckLake has replaced existing lakehouse systems.
As an affiliate, we earn on qualifying purchases.
How DuckLake Stores Table Data
In a lakehouse architecture, data is commonly held in files while metadata describes the tables and their organization. DuckLake’s documentation sets out that division directly: catalog database for metadata, and Parquet files for data. DuckDB’s extension provides the SQL-facing means to attach to that arrangement and issue table operations.
The repository includes testing instructions that point to multiple catalog configurations. It lists tests using DuckLake as a storage backend, as well as configurations for PostgreSQL and SQLite catalogs and tests with deletion vectors enabled. This shows that the project documents testing across those setups; it does not, by itself, establish the full range of supported production configurations or guarantee that every feature behaves identically in each one.
The project invites external contributions and says its active development branch is main. It also warns that building against moving submodule branches can fail, while its pinned submodules correspond to a DuckDB version recorded in the repository. Those details place the extension in an actively maintained software-development workflow, but the source provided does not state a version number or formal stability level.
“DuckLake is an open Lakehouse format that is built on SQL and Parquet.”
— DuckLake GitHub repository
As an affiliate, we earn on qualifying purchases.
Release Status and Compatibility Details
The supplied repository material does not identify when DuckLake or the extension was released, name a stable version, or say whether the extension is ready for production use. It also provides no benchmark results, service-level guarantees, adoption figures or independent assessment of reliability.
Although the documentation lists PostgreSQL and SQLite catalog test configurations, it does not fully define which catalog and storage combinations are supported, or describe their limitations. The examples demonstrate particular operations and outputs; they should not be taken as a complete specification of behavior for every workload. The source material also does not explain a full compatibility matrix with other lakehouse tools.
As an affiliate, we earn on qualifying purchases.
Development and Testing Ahead
The repository points readers to its usage guide for additional instructions and welcomes outside contributions to the active main branch. Its build and test commands provide a route for developers to compile the extension and run tests, including tests configured for different catalog databases.
No next release, launch date or roadmap milestone is stated in the supplied material. Readers tracking the project will need to consult the repository for later version information, documentation changes and development updates. Until those details are published, the documented SQL operations and test configurations are the clearest available indicators of what the extension currently presents.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is DuckLake?
DuckLake is described by its project as an open lakehouse format built on SQL and Parquet. It stores metadata in a catalog database and table data in Parquet files.
What does the DuckDB extension do?
The extension lets DuckDB read and write DuckLake data. Users can attach a DuckLake database and then create, modify and query tables using SQL.
Which features does the documentation show?
The examples cover table creation, inserts, updates, adding a column, reading an earlier version and querying a change-data feed. The examples illustrate documented operations, not every capability or limitation.
Does the source confirm that DuckLake is production-ready?
No. The supplied documentation does not state a formal stability level or production-readiness status. It includes installation and testing instructions, but those do not establish a support guarantee.
When was the extension released?
The source material does not give an announcement date or release date. It points to the GitHub repository for installation instructions and ongoing development information.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
