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 users attach DuckLake databases and read or write their tables using DuckDB and standard SQL. The project documentation describes metadata stored in a catalog database and table data stored in Parquet files, alongside features such as time travel and change-data queries.
DuckDB’s DuckLake extension allows the database engine to read and write data in DuckLake, an open lakehouse format that stores metadata in a catalog database and table data in Parquet files. The project documentation describes attaching a DuckLake database and then using standard SQL to create, query and modify its tables.
The extension’s documented setup uses DuckDB’s INSTALL ducklake; command. Users can attach a DuckLake database with an ATTACH statement, specifying a metadata database and a path for the Parquet data. The example in the project repository uses a local DuckDB database file for the catalog, though the documentation also includes test configurations for PostgreSQL and SQLite catalogs.
Once attached, a DuckLake database can be used for familiar SQL operations. The examples create a table, insert rows, query the result and update a value. The documentation also demonstrates schema changes, adding a column, and querying an earlier version of a table with DuckLake’s time-travel syntax.
The repository further shows a change data feed query that returns records with snapshot identifiers, row IDs and change types. These examples document the kinds of operations the extension supports; they do not provide independent performance results or a comparison with other lakehouse systems. The project provides instructions for building the extension and running tests, including configurations for different catalog databases and for deletion vectors.
SQL Access to Parquet Lake Data
The extension connects DuckDB’s SQL workflow with a storage layout built around Parquet files and a separate metadata catalog. For users who want to work with DuckLake data through DuckDB, the documented attach-and-query pattern means they can use SQL for reading and writing rather than treating the files as an isolated collection.
Version history and change-data queries may also help with tasks that depend on understanding how tables changed over time. The documentation shows these capabilities, but it does not establish how they perform at scale or what operational requirements apply in different deployments. The practical importance will depend on a user’s catalog setup, data location, workload and compatibility needs.
Products Worth Considering
LG UltraGear 32GX850A-B 32-Inch 4K UHD Glossy OLED Gaming Monitor
DJI Osmo Pocket 3 Vlogging Camera with 1-Inch CMOS Sensor and 4K Video
Sony WH-1000XM6 Wireless Noise-Canceling Over-Ear Headphones, Blue, Bundle
As an affiliate, we earn on qualifying purchases.
How DuckLake Stores Tables
DuckLake is described by its project as an open lakehouse format built on SQL and Parquet. Its design separates the catalog, which holds metadata, from Parquet files, which hold table data. DuckDB’s extension is the connector that lets DuckDB directly read and write that format.
The repository presents DuckLake as an actively developed extension: it identifies main as the active development branch and invites outside contributions. It also gives build and test instructions. The supplied source does not identify a dated launch announcement, a specific release number or a change from an earlier version, so this report describes the documented project capability rather than a newly dated product launch.
“DuckLake is an open Lakehouse format that is built on SQL and Parquet.”
— DuckLake project documentation on GitHub
Release and Deployment Details
The supplied repository material does not state when the extension was released, which version the documentation covers, or whether the described capabilities are available in a particular stable DuckDB release. It also provides no benchmarks, production case studies, or detailed limits for table size, concurrency and catalog behavior.
The examples show a local DuckDB file used as a catalog and list PostgreSQL and SQLite test configurations. They do not, by themselves, explain the full deployment requirements or establish that every catalog option is equally suitable for production. Users should consult the current usage guide and version-specific documentation before relying on a feature or configuration.
Check Versions and Usage Guidance
The project repository points readers to a usage guide for fuller instructions and provides commands for installing the extension, including a command to install a development build from the core_nightly repository. The supplied material does not announce a release date or describe a scheduled next milestone.
For users evaluating DuckLake, the next practical step is to check the current DuckDB and extension documentation, select a supported catalog and data path, and test the needed operations in their own environment. The repository’s test instructions offer examples for exercising DuckLake with DuckDB, PostgreSQL or SQLite catalogs; they do not substitute for workload-specific evaluation.
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 DuckLake extension do?
The extension lets DuckDB read and write DuckLake data. After attaching a DuckLake database, users can work with its tables using SQL operations shown in the project documentation.
Does DuckLake support time travel?
The documentation includes a query that reads a table at a specified version, demonstrating time-travel functionality. The supplied material does not set out all version-retention rules or limits.
Which catalog databases are mentioned?
The usage example stores metadata in a DuckDB database file. The repository also provides test configurations for PostgreSQL and SQLite catalogs; the source does not establish that every option has the same deployment requirements.
Is this a newly announced release?
The supplied source is project documentation and does not give a release date or version number. It confirms the extension’s documented functionality but is not enough to establish a newly announced release.
Source: hn
