beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henning Rohde (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-2880) Artifact server proxies
Date Fri, 21 Sep 2018 17:04:00 GMT

    [ https://issues.apache.org/jira/browse/BEAM-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623884#comment-16623884
] 

Henning Rohde commented on BEAM-2880:
-------------------------------------

Based on the portable Flink runner work, it seems these proxies are not the direction that
we want to go. I'll close the this issue and remove the (unused) sketch code. We can always
revive that path later.

> Artifact server proxies
> -----------------------
>
>                 Key: BEAM-2880
>                 URL: https://issues.apache.org/jira/browse/BEAM-2880
>             Project: Beam
>          Issue Type: Improvement
>          Components: beam-model
>            Reporter: Henning Rohde
>            Priority: Minor
>              Labels: portability
>
> As per https://s.apache.org/beam-fn-api-container-contract, we should add runner-agnostic
(dockerized) artifact proxies for various runner environments. These proxies implement the
server side of the artifact API.
> We'll likely need proxies for GCS, S3, Azure Storage, and local. If the proxies are implemented
in a statically-linked language like Go, say, then they do not have a dependency footprint
and can easily be used as native binaries or in dockerized form -- at the discretion of the
runner.



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

Mime
View raw message