From 1f8f096f8d71928b37efad5e6102d0fe71437dc0 Mon Sep 17 00:00:00 2001 From: FAQ Bot Date: Thu, 12 Mar 2026 11:45:37 +0000 Subject: [PATCH] NEW: Why does the tumbling window job run successfully but the PostgreSQL sin --- .../006_29e617a947_tumbling-window-sink-empty-results.md | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 _questions/data-engineering-zoomcamp/module-7/006_29e617a947_tumbling-window-sink-empty-results.md diff --git a/_questions/data-engineering-zoomcamp/module-7/006_29e617a947_tumbling-window-sink-empty-results.md b/_questions/data-engineering-zoomcamp/module-7/006_29e617a947_tumbling-window-sink-empty-results.md new file mode 100644 index 0000000..abd0207 --- /dev/null +++ b/_questions/data-engineering-zoomcamp/module-7/006_29e617a947_tumbling-window-sink-empty-results.md @@ -0,0 +1,8 @@ +--- +id: 29e617a947 +question: Why does the tumbling window job run successfully but the PostgreSQL sink + table returns no rows when queried? +sort_order: 6 +--- + +Flink streaming jobs emit results only after the window closes. With event-time processing and watermarks, the window will not close until the watermark passes the window end. If you query the PostgreSQL table too early, it may still be empty even though the job is running correctly. Let the job run for a short time so the watermark advances and the window results are written to the sink table. \ No newline at end of file