duckdb/ducklake

DuckLake is an integrated data lake and catalog format

View on GitHub ↗Jump to charts ↓Open shareable report →

duckdb/ducklake has 3k+ stars and 250+ forks on GitHub, is written in C++, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 42 minutes ago
Added to GitGenius on September 24th, 2026
Created on March 3rd, 2025
Open Issues & Pull Requests: 41 (+0)
GitHub issues: Enabled
Number of forks: 286
Total Stargazers: 3,314 (+0)
Total Subscribers: 26 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 27.6 hours
Mean response time: 16.8 days
90th percentile: 40.8 days
Tracked items: 558

Maintainer activity

4 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 4% of issues opened in the past year have never received a reply. 94% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 92% of issues opened in the past year have since been closed. Three people close 73% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 33
New in 7 days: 12
Closed in 7 days: 7
Avg open age: 134 days
Stale 30+ days: 18
Stale 90+ days: 9

Recent activity

Opened in 7 days: 9
Closed in 7 days: 6
Comments in 7 days: 1
Events in 7 days: 2

Top labels

  • needs triage (198)
  • reproduced (48)
  • needs reproducible example (27)
  • enhancement (15)
  • question (13)
  • under review (11)
  • PR submitted (10)
  • expected behavior (8)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

DuckLake is an open Lakehouse format built on SQL and Parquet that integrates with DuckDB as an extension.

DuckLake addresses the need for a unified data lake and catalog system by storing metadata in a catalog database and data in Parquet files. The approach allows DuckDB to read and write data directly through standard SQL operations. Users attach DuckLake databases using SQL syntax and then create, modify, and query tables as they would in any relational database. The format supports updates, time travel, schema evolution, and change data feeds as core capabilities.

DuckLake suits projects that want lakehouse functionality without adopting a separate ecosystem. It is designed for teams already using DuckDB who need catalog and metadata management alongside their Parquet-based data storage. The tight integration with DuckDB means users work entirely within SQL rather than learning additional APIs or tools. This approach is particularly relevant for analytics workloads where schema flexibility and historical data access matter.

The project maintains an active development branch and welcomes external contributions. Development activity shows ongoing work to expand the extension's capabilities and integration with DuckDB's ecosystem.