[
https://issues.apache.org/jira/browse/BEAM-6248?focusedWorklogId=179810&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-179810
]
ASF GitHub Bot logged work on BEAM-6248:
----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Dec/18 17:24
Start Date: 30/Dec/18 17:24
Worklog Time Spent: 10m
Work Description: mxm commented on issue #7300: [BEAM-6248] Add Flink
v1.7 build target to Flink Runner
URL: https://github.com/apache/beam/pull/7300#issuecomment-450574857
>You mentioned that tests for multiple Flink versions should run
sequentially. Are you going to address it as part of this PR?
Yes, this has to be done in this PR. Otherwise, we get OutOfMemoryException
due to three Flink clusters running. I haven't come up with an elegant way of
doing it. Alternatively, decreasing the parallelism could also help, it's
usually 16 on Jenkins.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 179810)
Time Spent: 3h (was: 2h 50m)
> Add Flink 1.7.x build target to Flink Runner
> --------------------------------------------
>
> Key: BEAM-6248
> URL: https://issues.apache.org/jira/browse/BEAM-6248
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Major
> Fix For: 2.10.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> With BEAM-5419 we can add a Flink 1.7.x build target.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
