[
https://issues.apache.org/jira/browse/BEAM-7012?focusedWorklogId=233622&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-233622
]
ASF GitHub Bot logged work on BEAM-7012:
----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Apr/19 15:58
Start Date: 26/Apr/19 15:58
Worklog Time Spent: 10m
Work Description: mxm commented on issue #8383: [BEAM-7012] Support
TestStream in streaming Flink Runner
URL: https://github.com/apache/beam/pull/8383#issuecomment-487109427
Yes, I was wondering about quiescence as well. It looks to me that it is
nice to have but not necessary when a strict order of all TestStream events can
be guaranteed. I see that quiescence in the case of Dataflow is necessary
because of the global watermark service for which we cannot update the
watermark unless elements have been fully processed. Flink's Watermarks are
propagated through the graph just like regular data elements (in case of
multiple outputs of a operator they will be send to each of the outputs). Thus,
any events triggered by the TestStream source are guaranteed to be processed
one after another and should not influence each other.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 233622)
Time Spent: 3h 20m (was: 3h 10m)
> Support TestStream in FlinkRunner
> ---------------------------------
>
> Key: BEAM-7012
> URL: https://issues.apache.org/jira/browse/BEAM-7012
> Project: Beam
> Issue Type: New Feature
> Components: runner-flink
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Major
> Fix For: 2.13.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> TestStream is a primitive transform which is only supported by the
> DirectRunner. It might be useful to also implement it in the Flink Runner to
> run similar kind of tests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
