[
https://issues.apache.org/jira/browse/BEAM-12277?focusedWorklogId=594461&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-594461
]
ASF GitHub Bot logged work on BEAM-12277:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 11/May/21 10:24
Start Date: 11/May/21 10:24
Worklog Time Spent: 10m
Work Description: dmvk commented on pull request #14719:
URL: https://github.com/apache/beam/pull/14719#issuecomment-838227077
I think this boils down to whether we want to wait for the issue being fixed
in Flink or we want a "quick-win" solution 🤔
Maybe we can temporarily work around this in
[FileReporter](https://github.com/apache/beam/blob/master/runners/flink/src/main/java/org/apache/beam/runners/flink/metrics/FileReporter.java#L69),
before fixing the issue upstream?
--
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: 594461)
Time Spent: 10.5h (was: 10h 20m)
> Add flink 1.13 build target
> ---------------------------
>
> Key: BEAM-12277
> URL: https://issues.apache.org/jira/browse/BEAM-12277
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
> Reporter: David Morávek
> Assignee: David Morávek
> Priority: P2
> Time Spent: 10.5h
> Remaining Estimate: 0h
>
> Add support for flink 1.13
--
This message was sent by Atlassian Jira
(v8.3.4#803005)