[
https://issues.apache.org/jira/browse/BEAM-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17131946#comment-17131946
]
Beam JIRA Bot commented on BEAM-2262:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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
> Priority: P2
> Labels: stale-P2
>
> 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
(v8.3.4#803005)