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/01/12 03:50:05 UTC

[jira] [Updated] (BEAM-4286) Pooled artifact source

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

Kenneth Knowles updated BEAM-4286:
----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> Pooled artifact source
> ----------------------
>
>                 Key: BEAM-4286
>                 URL: https://issues.apache.org/jira/browse/BEAM-4286
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>            Reporter: Ben Sidhom
>            Priority: P3
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Because DistributeCache lifetimes are tied to operator lifetimes in Flink, we need a way to wrap operator-scoped artifact sources. Artifacts are inherently job-scoped and should be the same throughout a job's lifetime. For this reason, it is safe to pool artifact sources and serve artifacts from an arbitrary pooled source as long as the underlying source is still in scope.
> We need a pooled source in order to satisfy the bundle factory interfaces. Using the job-scoped and stage-scoped bundle factories allows us to cache and reuse different components that serve SDK harnesses. Because the distributed cache lifetimes are specific to Flink, the pooled artifact source should probably live in a runner-specific directory.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)