beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Amato (JIRA)" <>
Subject [jira] [Commented] (BEAM-210) Be consistent with emitting final empty panes
Date Tue, 19 Apr 2016 18:40:25 GMT


Alex Amato commented on BEAM-210:

The user that discovered this is reporting that they output the same result for the window
multiple times, suggesting that they are receiving a firing for the same data.

This may be a combination of using afterprocesingtime and afterwatermark together.

> Be consistent with emitting final empty panes
> ---------------------------------------------
>                 Key: BEAM-210
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core
>            Reporter: Mark Shields
>            Assignee: Mark Shields
> Currently ReduceFnRunner.onTrigger uses shouldEmit to prevent empty final panes unless
the user has requested them.
> The same check needs to be done in ReduceFnRunner.onTimer

This message was sent by Atlassian JIRA

View raw message