[jira] [Resolved] (BEAM-8660) Override returned artifact staging endpoint

["Kyle Weaver (Jira)" <ji...@apache.org>]

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

Kyle Weaver resolved BEAM-8660.
-------------------------------
    Fix Version/s: 2.18.0
       Resolution: Fixed

> Override returned artifact staging endpoint
> -------------------------------------------
>
>                 Key: BEAM-8660
>                 URL: https://issues.apache.org/jira/browse/BEAM-8660
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-flink
>            Reporter: Kyle Weaver
>            Assignee: Kyle Weaver
>            Priority: Major
>              Labels: portability-flink
>             Fix For: 2.18.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When running Beam Python pipelines on Flink/Spark/etc, we connect the SDK to the job server using the job_endpoint option. The job server then returns the address of the artifact staging endpoint to the SDK.
> This is problematic when running the job server in network environments where the job server is not aware of its external hostname, for example Kubernetes. In this case, the job server will return something like localhost:8098, which might not be correct. While we do have a --job-host option, this is used both internally and externally, and the internal and external host names may not be the same.
> One solution would be to configure two separate host names in the job server. However I do not prefer this option because of the complexity it adds.
> The more straightforward solution is to add an option to Python that overrides the artifact staging endpoint returned by the server.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)