Skip to content

[FAQ Bot] NEW: Why does the tumbling window job run successfully but the PostgreSQL sin #247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[FAQ Bot] NEW: Why does the tumbling window job run successfully but the PostgreSQL sin #247

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions ...ineering-zoomcamp/module-7/006_29e617a947_tumbling-window-sink-empty-results.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.