beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1316) DoFn#startBundle should not be able to output
Date Thu, 04 May 2017 22:56:04 GMT

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

ASF GitHub Bot commented on BEAM-1316:
--------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/beam/pull/2695


> DoFn#startBundle should not be able to output
> ---------------------------------------------
>
>                 Key: BEAM-1316
>                 URL: https://issues.apache.org/jira/browse/BEAM-1316
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Thomas Groh
>            Assignee: Thomas Groh
>              Labels: backward-incompatible
>             Fix For: First stable release
>
>
> While within startBundle and finishBundle, the window in which elements are output is
not generally defined. Elements must always be output from within a windowed context, or the
{{WindowFn}} used by the {{PCollection}} may not operate appropriately.
> startBundle and finishBundle are suitable for operational duties, similarly to {{setup}}
and {{teardown}}, but within the scope of some collection of input elements. This includes
actions such as clearing field state within a DoFn and ensuring all live RPCs complete successfully
before committing inputs.
> Sometimes it might be reasonable to output from {{@FinishBundle}} but it is hard to imagine
a situation where output from {{@StartBundle}} is useful in a way that doesn't seriously abuse
things.



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

Mime
View raw message