I could imagine an "UniversalJavaClient" that is parameterized by the
actual runner itself dynamically. But it may also make sense for
Flink, Spark, etc. managers to serve this API directly when part of a
service.

On Mon, Feb 12, 2018 at 4:22 PM, Thomas Weise (JIRA) <j...@apache.org> wrote:
>
>     [ 
> https://issues.apache.org/jira/browse/BEAM-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361635#comment-16361635
>  ]
>
> Thomas Weise commented on BEAM-2591:
> ------------------------------------
>
> [~kenn] will the "production/portable endpoint" be provided by the "Flink 
> Client JVM" in [https://s.apache.org/portable-flink-runner-overview] and is 
> the assumption that every runner will implement such a client JVM?
>
>> Python shim for submitting to FlinkRunner
>> -----------------------------------------
>>
>>                 Key: BEAM-2591
>>                 URL: https://issues.apache.org/jira/browse/BEAM-2591
>>             Project: Beam
>>          Issue Type: Sub-task
>>          Components: runner-flink, sdk-py-core
>>            Reporter: Kenneth Knowles
>>            Priority: Major
>>              Labels: portability
>>
>> Whatever the result of https://s.apache.org/beam-job-api, Python users will 
>> need to be able to pass --runner=FlinkRunner and have it work.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)

Reply via email to