You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Danny McCormick (Jira)" <ji...@apache.org> on 2022/06/03 15:08:00 UTC

[jira] [Commented] (BEAM-311) Add 'garbage collection' hold when receive late element

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

Danny McCormick commented on BEAM-311:
--------------------------------------

This isn't actually real, but this issue has been migrated to https://github.com/apache/beam/issues/17856

> Add 'garbage collection' hold when receive late element
> -------------------------------------------------------
>
>                 Key: BEAM-311
>                 URL: https://issues.apache.org/jira/browse/BEAM-311
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core
>            Reporter: Mark Shields
>            Priority: P3
>
> We currently add a 'garbage collection' hold in WatermarkHold (invoked via ReduceFnRunner) if the closing behavior is FIRE_ALWAYS. This means an element which has come in too late for a data holds and an end-of-window hold may end up setting no hold at all. As a result, the eventual pane containing that element may end up dropped as being too late.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)