[BEAM-7825] Python's DirectRunner emits multiple panes per window and does not discard late data

• Type: Bug
• Status: Open
• Priority: P3
• Resolution: Unresolved
• Affects Version/s: 2.13.0
• Component/s: sdk-py-core
• Environment: OS: Debian rodete. ; Beam versions: 2.15.0.dev. ; Python versions: Python 2.7, Python 3.7
• Assignee: Unassigned
• Reporter: Alexey Strokach
• Created: 26/Jul/19 04:08
• Updated: 04/Jun/22 12:57

Description

The documentation for Beam's Windowing and Triggers functionality states that "if you use Beam’s default windowing configuration and default trigger, Beam outputs the aggregated result when it estimates all data has arrived, and discards all subsequent data for that window". However, it seems that the current behavior of Python's DirectRunner is inconsistent with both of those points. As the StreamingWordGroupIT.test_discard_late_data test shows, DirectRunner appears to process every data point that it reads from the input stream, irrespective of whether or not the timestamp of that data point is older than the timestamps of the windows that have already been processed. Furthermore, as the StreamingWordGroupIT.test_single_output_per_window test shows, DirectRunner generates multiple "panes" for the same window, apparently disregarding the notion of a watermark?

The Dataflow runner passes both of those end-to-end tests.

Issue Links

• links to: GitHub Pull Request #9164