Skip to content

feat(gizmosql): store the lakehouse in ducklake - #339

Merged
dargmuesli merged 3 commits into
feat/gizmosql/addfrom
feat/gizmosql/ducklake
Nov 11, 2026
Merged

dargmuesli merged 3 commits into
feat/gizmosql/addfrom
feat/gizmosql/ducklake

Conversation

@dargmuesli

Copy link
Copy Markdown
Member

Builds on #289 and moves the lakehouse from plain Parquet files to DuckLake, with the catalog in a dedicated ducklake Postgres database and the data files on R2. Redpanda Connect now consumes vibetype.outbox.event and vibetype.outbox.account and lands the envelopes as Parquet, and a gizmosql-maintenance service registers new files every minute, erases the rows of deleted accounts, and runs an hourly checkpoint for compaction, snapshot expiry and file cleanup. Snapshots are kept for 7 days, which bounds both time travel for auditing and how long erased data stays on storage. The operation column of analytics.events now holds the outbox event type instead of Debezium's operation letter.

Depends on maevsi/sqitch#356 for the catalog database and on #294 for the outbox topics.

@dargmuesli
dargmuesli requested a review from HMDank November 11, 2026 08:21
@dargmuesli
dargmuesli merged commit c79716d into feat/gizmosql/add Nov 11, 2026
5 checks passed
@dargmuesli
dargmuesli deleted the feat/gizmosql/ducklake branch November 11, 2026 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant