[
https://issues.apache.org/jira/browse/BEAM-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830683#comment-15830683
]
Kenneth Knowles commented on BEAM-1282:
---------------------------------------
Agree about {{startBundle}}; I wonder if there are use cases out there... and I
don't know of any use case for outputting in {{finishBundle}} that is not
better addressed via state (in its infancy) and window expiry callbacks (easy,
obvious, but unimplemented). So I think it is fine for {{DoFnTester}} to take a
{{WindowFn}} for such outputs until such time as we decide to fix BEAM-1283.
> DoFnTester should allow output() calls in start/finishBundle
> ------------------------------------------------------------
>
> Key: BEAM-1282
> URL: https://issues.apache.org/jira/browse/BEAM-1282
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Daniel Mills
> Priority: Minor
> Labels: starter
>
> In a DoFn, users can call output() or outputWithTimestamp() during
> start/finishBundle. This will attempt to deduce a window for the output
> element based on the current WindowFn and any timestamp provided. However,
> DoFnTester always throws an exception if these methods are called from
> start/finishBundle (because it does not have a WindowFn, so that will have to
> be enhanced)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
