beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmet Altay (JIRA)" <>
Subject [jira] [Commented] (BEAM-1316) DoFn#startBundle should not be able to output
Date Tue, 02 May 2017 17:08:04 GMT


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:
>             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

This message was sent by Atlassian JIRA

View raw message