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] [Resolved] (BEAM-2880) Artifact server proxies
Date Sat, 22 Sep 2018 15:45:00 GMT

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

Henning Rohde resolved BEAM-2880.
---------------------------------
       Resolution: Won't Fix
    Fix Version/s: Not applicable

> 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
>            Assignee: Henning Rohde
>            Priority: Minor
>              Labels: portability
>             Fix For: Not applicable
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> 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