[
https://issues.apache.org/jira/browse/BEAM-2930?focusedWorklogId=135737&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-135737
]
ASF GitHub Bot logged work on BEAM-2930:
----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Aug/18 16:18
Start Date: 17/Aug/18 16:18
Worklog Time Spent: 10m
Work Description: tweise commented on issue #6208: [WIP] [BEAM-2930] Side
input support for Flink portable streaming.
URL: https://github.com/apache/beam/pull/6208#issuecomment-413916534
What is supposed to happen when the windowing strategy allows early/repeated
firing? Won't that lead to indeterministic behavior?
If repeated firing is possible, then my current approach of just
accumulating records into an Iterable won't work.
With the non portable runner, views are materialized via combine. While that
would ensure that the Iterable is constructed correctly, repeated firing would
still lead to indeterministic results. Anyone with better understanding of the
old Flink runner can offer any insight here?
https://github.com/apache/beam/blob/master/runners/flink/src/main/java/org/apache/beam/runners/flink/CreateStreamingFlinkView.java#L52
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 135737)
Time Spent: 3.5h (was: 3h 20m)
> Flink support for portable side input
> -------------------------------------
>
> Key: BEAM-2930
> URL: https://issues.apache.org/jira/browse/BEAM-2930
> Project: Beam
> Issue Type: Sub-task
> Components: runner-flink
> Reporter: Henning Rohde
> Priority: Major
> Labels: portability
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
