You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/05/15 16:15:00 UTC
[jira] [Work logged] (BEAM-6733) Use Flink 1.6/1.7
prepareSnapshotPreBarrier to replace BufferedOutputManager
[ https://issues.apache.org/jira/browse/BEAM-6733?focusedWorklogId=433749&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-433749 ]
ASF GitHub Bot logged work on BEAM-6733:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/May/20 16:14
Start Date: 15/May/20 16:14
Worklog Time Spent: 10m
Work Description: mxm commented on pull request #11678:
URL: https://github.com/apache/beam/pull/11678#issuecomment-629348473
Run Java PreCommit
----------------------------------------------------------------
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:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 433749)
Time Spent: 3h 10m (was: 3h)
> Use Flink 1.6/1.7 prepareSnapshotPreBarrier to replace BufferedOutputManager
> ----------------------------------------------------------------------------
>
> Key: BEAM-6733
> URL: https://issues.apache.org/jira/browse/BEAM-6733
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Minor
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> Flink 1.6/1.7 provides a hook to execute an action before the snapshot barrier is emitted by the operator. At the moment (<=1.5) the Flink Runner has to buffer any elements which are emitted during a snapshot because the barrier has already been emitted. This leads to a lot of code complexity.
> We can remove the buffering in favor of finishing the current bundle in {{DoFnOperator}}'s {{prepareSnapshotPreBarrier}}. The 1.5/1.6/1.7 build setup poses a challenge to do that in a way that does not lead to much code duplication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)