You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2017/05/11 19:33:05 UTC

[jira] [Commented] (BEAM-2262) TimestampCombiner.EARLIEST is not respected when elements are late.

    [ https://issues.apache.org/jira/browse/BEAM-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007051#comment-16007051 ] 

Kenneth Knowles commented on BEAM-2262:
---------------------------------------

Technically, WAI according to design docs, but those designs are now obsolete. The actual description in GBK implies the behavior that you are expecting (and users will expect) so we can fix this after 2.0.0 and consider it backwards compatible / a bug fix.

> TimestampCombiner.EARLIEST is not respected when elements are late.
> -------------------------------------------------------------------
>
>                 Key: BEAM-2262
>                 URL: https://issues.apache.org/jira/browse/BEAM-2262
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core
>    Affects Versions: 2.0.0
>            Reporter: Thomas Groh
>
> In ReduceFnRunner#onTrigger, because late elements don't set a hold, we do not output with the timestamp that would be expected by the TimestampCombiner.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)