Summary:
We configured Lakebase CDF to stream changes from a native Postgres table (public.query_logs) into Unity Catalog, but the destination Delta table never appears despite completing all documented prerequisites.
Steps taken
1. Created query_logs in Lakebase and confirmed rows are written successfully (application INSERTs work).
2. Ran ALTER TABLE query_logs REPLICA IDENTITY FULL; and verified replica identity.
Enabled Lakebase CDF in the branch UI: source schema public, destination UC catalog/schema configured, target table name lb_query_logs_history.
3. UI shows CDF as started; we waited for initial snapshot / streaming.
4. Verified from Databricks: spark.table("<catalog>.default.lb_query_logs_history") fails — table not found in Catalog Explorer.
Expected: A UC-managed Delta table (e.g. lb_query_logs_history) with CDF metadata columns (_pg_change_type, _timestamp, etc.) reflecting inserts into query_logs.
Actual: No destination Delta table in UC. Querying Lakebase wal2delta.tables also shows no usable destination. Source table continues to receive writes normally.
Questions:
Is this a known Free Edition limitation, or a bug?
Any required diagnostics or support steps we should run?
Thank you.😊😊
