beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-4130) Portable Flink runner JobService entry point in a Docker container
Date Thu, 06 Sep 2018 08:47:00 GMT


ASF GitHub Bot logged work on BEAM-4130:

                Author: ASF GitHub Bot
            Created on: 06/Sep/18 08:46
            Start Date: 06/Sep/18 08:46
    Worklog Time Spent: 10m 
      Work Description: mxm commented on a change in pull request #6341: [BEAM-4130] Fixing
bug in flink job server creation

 File path: runners/flink/src/main/java/org/apache/beam/runners/flink/
 @@ -130,7 +137,7 @@ private FlinkJobServerDriver(
     this.configuration = configuration;
     this.executor = executor;
     this.jobServerFactory = jobServerFactory;
-    this.artifactServerFactory = jobServerFactory;
+    this.artifactServerFactory = artifactServerFactory;
 Review comment:
   Thanks for spotting this.

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:

Issue Time Tracking

    Worklog Id:     (was: 141673)
    Time Spent: 8h 20m  (was: 8h 10m)

> Portable Flink runner JobService entry point in a Docker container
> ------------------------------------------------------------------
>                 Key: BEAM-4130
>                 URL:
>             Project: Beam
>          Issue Type: New Feature
>          Components: runner-flink
>            Reporter: Ben Sidhom
>            Assignee: Maximilian Michels
>            Priority: Minor
>             Fix For: 2.7.0
>          Time Spent: 8h 20m
>  Remaining Estimate: 0h
> The portable Flink runner exists as a Job Service that runs somewhere. We need a main
entry point that itself spins up the job service (and artifact staging service). The main
program itself should be packaged into an uberjar such that it can be run locally or submitted
to a Flink deployment via `flink run`.

This message was sent by Atlassian JIRA

View raw message