You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Ahmet Altay (JIRA)" <ji...@apache.org> on 2017/05/02 17:08:04 UTC

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

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

Ahmet Altay commented on BEAM-1316:
-----------------------------------

[~sb2nov] could we remove the sdk-py component from this issues if it is fixed for python? (for tracking purposes.)

> 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, sdk-py
>            Reporter: Thomas Groh
>            Assignee: Thomas Groh
>             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)