You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Thomas Groh (JIRA)" <ji...@apache.org> on 2017/01/25 23:01:26 UTC

[jira] [Commented] (BEAM-1316) DoFn#startBundle and #finishBundle should not be able to output

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

Thomas Groh commented on BEAM-1316:
-----------------------------------

Forbidding output from startBundle and finishBundle brings the contexts received by them in line with setup and teardown

> DoFn#startBundle and #finishBundle 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
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)