Timelaketimelake
DocsBenchmarksRoadmapSpecContribute
Apache 2.0 ·
Roadmap

DoneIn progressPlanned

Tables and storage

Done:1. Iceberg tablesDone:2. CommitsDone:3. Object-store catalogIn progress:4. Time-series table contractIn progress:5. File layout and encodingsIn progress:6. Last-value indexDone:7. One-request table state and version checksDone:8. Table format versions and upgradesDone:9. SettingsPlanned:10. Supplemental timestamps

Writing

Done:11. AppendsDone:12. Late data and dedup on readDone:13. Writes from WebAssemblyPlanned:14. Hot tier and seconds-fresh readsPlanned:15. BackfillIn progress:16. Import and migrationPlanned:17. DeletesPlanned:18. GDPR erasure

Maintenance

Done:19. CompactionIn progress:20. Maintenance runs, retention and expiry

Reading

In progress:21. Timelake readerDone:22. Block cacheDone:23. Filter pushdownDone:24. Pruning with long IN listsDone:25. Newest-first scansDone:26. Scans in series orderDone:27. Materialized rollups

SQL functions

In progress:28. Function libraryDone:29. Time buckets and gap fillingDone:30. Signal aggregatesDone:31. Downsampling with m4

Integrations

Planned:32. REST catalogPlanned:33. DuckDB extensionPlanned:34. Snowflake connectionPlanned:35. Multitenancy

Services

Planned:36. Ingestion and rulesPlanned:37. Data to eventsPlanned:38. Static read modelsPlanned:39. Computed metricsPlanned:40. Agent access with permission setsPlanned:41. Device syncPlanned:42. Edge gatewayPlanned:43. Server mode

Benchmarks

In progress:44. Benchmark harness: timebenchIn progress:45. Industrial IoT benchmarkPlanned:46. Agent benchmark

Background

ArchitectureDeployment and cost modelEmbedded engine: DataFusionLandscape and positioningLicense and open corePurpose and requirementsReleases
TimelaketimelakeThe open time-series lakehouse.
v0 · Apache 2.0 · Contribute · GitHubBuilt on Apache Arrow, Apache DataFusion, Apache Parquet, and Apache Iceberg.
DocsBenchmarksRoadmapSpecContribute

Spec 33 · Integrations

DuckDB extension

PlannedUpdated 2026-10-12View on GitHub
Versions
Not released yet
Roadmap
Any engine can attach, Technical preview
Related
1. Iceberg tables, 12. Late data and dedup on read, 14. Hot tier and seconds-fresh reads, 21. Timelake reader, 28. Function library

Summary

A loadable DuckDB extension that makes DuckDB Timelake-aware: dedup on read, index-aware scans, the hot tier, and the function library, with the same kernels as the Timelake reader. Plain DuckDB already reads every table (spec 1); the extension closes the gap to the Timelake reader for people who keep DuckDB.

Design

  • What it adds over plain DuckDB:
    • Dedup on read, so DuckDB doesn't see copies before compaction (spec 12; Q3, #106).
    • Index-aware scans: the last-value index, the head, and series pruning (spec 21).
    • Hot-tier merge for seconds-fresh reads (spec 14).
    • The function library with full parity (spec 28), and procedures such as CALL timelake_backfill(…) (spec 15).
  • One function implementation, two engines: time-series kernels live in an engine-agnostic crate on Arrow arrays. Thin adapters expose them as DataFusion UDFs/UDAFs and as DuckDB extension functions (Rust via the DuckDB C extension API; verify aggregate-function coverage).
  • Until then: a SQL macro pack for plain DuckDB (#127).

Open questions and issues

  • #128 DuckDB extension: dedup on read, index-aware scans and the function library

History

  • 2026-10-11: the DuckDB extension as the user-facing SQL path (SPEC.md §6, D3)
  • 2026-10-19: gathered from SPEC.md (specs 2, 5, 17 and 24) into this spec when the specs were regrouped one per feature.