You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/06/03 19:31: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=17546796#comment-17546796 ] 

Kenneth Knowles commented on BEAM-3672:
---------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/18627

> 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: Improvement
>          Components: runner-flink
>            Reporter: Ben Sidhom
>            Priority: P3
>
> 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
(v8.20.7#820007)