You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kyle Weaver (JIRA)" <ji...@apache.org> on 2019/03/01 21:28:00 UTC

[jira] [Updated] (BEAM-6725) Move runner-agnostic code out of FlinkJobInvocation

     [ https://issues.apache.org/jira/browse/BEAM-6725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kyle Weaver updated BEAM-6725:
------------------------------
    Fix Version/s: 2.12.0

> Move runner-agnostic code out of FlinkJobInvocation
> ---------------------------------------------------
>
>                 Key: BEAM-6725
>                 URL: https://issues.apache.org/jira/browse/BEAM-6725
>             Project: Beam
>          Issue Type: Task
>          Components: runner-flink, runner-samza, runner-spark
>            Reporter: Kyle Weaver
>            Assignee: Kyle Weaver
>            Priority: Major
>              Labels: portability
>             Fix For: 2.12.0
>
>          Time Spent: 6.5h
>  Remaining Estimate: 0h
>
> Like BEAM-6714, FlinkJobInvocation contains some code (for asynchronously running jobs) that isn't really Flink specific and therefore could/should be reused by other portable runners. I'm thinking instead of an interface, JobInvocation should be made an abstract class that implements the methods that it currently abstracts, with an abstract method `runPipeline` for the runner-specific details.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)