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

Posted to commits@beam.apache.org by "Axel Magnuson (JIRA)" <ji...@apache.org> on 2018/08/22 03:10:00 UTC

[jira] [Commented] (BEAM-3672) FlinkRunner: Implement an Artifact service using the Flink DistributedCache

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

Axel Magnuson commented on BEAM-3672:
-------------------------------------

Deprioritizing and unassigning this since there exists a viable ArtifactService that uses GCS, and it is an old work item that I'm not sure is worthwhile.

> FlinkRunner: Implement an Artifact service using the Flink DistributedCache
> ---------------------------------------------------------------------------
>
>                 Key: BEAM-3672
>                 URL: https://issues.apache.org/jira/browse/BEAM-3672
>             Project: Beam
>          Issue Type: Sub-task
>          Components: runner-flink
>            Reporter: Ben Sidhom
>            Assignee: Axel Magnuson
>            Priority: Minor
>
> We need to have a DistributedCache-based artifact service to ship with the portable Flink runner. The DistributedCache is a perfect fit for Flink because it comes for free and is the mechanism that Flink already uses to distribute its own artifacts.
>  
> The final artifact service implementation should be pluggable, but using the DistributedCache allows the Flink runner to work without additional external dependencies (beyond perhaps Docker).



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