Recommended path for streaming ingestion into DuckLake? #1252
Unanswered
spcvalente
asked this question in
Q&A
Replies: 2 comments
|
Hi! Don't have a real answer to the question, just a comment on this bit:
Using JDBC |
0 replies
|
Would sql-flow fit your use case? It is a Kafka consumer! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hey team 👋
First off — DuckLake is genuinely exciting. Massive congrats to the team.
I've been trying to figure out the recommended way to stream data into DuckLake and I'm hitting a wall. Here's what I found so far:
inyo-global/ducklake-kafka-connect— looks promising but the last commit was March 2026, the S3 integration test is disabled, and from what I can tell PostHog (the main adopter?) ended up replacing it with their own thing. Doesn't feel production-ready.PostHog/millpond— cleaner, actively maintained, but it's one-table-per-deployment and JSON-only. Good for their use case, not general-purpose.ducklake_add_data_files— cool escape hatch, but basically "write Parquet externally and register it," which pushes the problem upstream.pg_duckpipe— neat Postgres WAL approach, but Postgres-specific obviously.So my questions:
Ideally for us the answer would be Kafka — but open to whatever the team thinks is the right primitive here.
Thanks!
All reactions