[FAQ Bot] NEW: Why does the tumbling window job run successfully but the PostgreSQL sin#247
Open
github-actions[bot] wants to merge 1 commit intomainfrom
Open
[FAQ Bot] NEW: Why does the tumbling window job run successfully but the PostgreSQL sin#247github-actions[bot] wants to merge 1 commit intomainfrom
github-actions[bot] wants to merge 1 commit intomainfrom
Conversation
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✨ FAQ NEW
Course: data-engineering-zoomcamp
Section: module-7 (This topic covers Flink event-time tumbling windows and sink write timing, fitting Module 7: Streaming with Kafka.)
Related Issue: #246
Question
Why does the tumbling window job run successfully but the PostgreSQL sink table returns no rows when queried?
Decision Rationale
The proposal describes a Flink streaming window behavior not currently covered by existing FAQs in Module 7; it explains why the PostgreSQL sink may appear empty initially, which is not present in the current entries.
Placement Details
module-7tumbling-window-sink-empty-results🤖 Generated by FAQ Bot
Closes #246