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

Posted to issues@beam.apache.org by "Brian Hulette (Jira)" <ji...@apache.org> on 2020/05/29 19:14:00 UTC

[jira] [Resolved] (BEAM-10078) uniquify Dataflow specific jars when staging

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

Brian Hulette resolved BEAM-10078.
----------------------------------
    Resolution: Fixed

> uniquify Dataflow specific jars when staging
> --------------------------------------------
>
>                 Key: BEAM-10078
>                 URL: https://issues.apache.org/jira/browse/BEAM-10078
>             Project: Beam
>          Issue Type: Improvement
>          Components: cross-language, runner-dataflow
>            Reporter: Heejong Lee
>            Assignee: Heejong Lee
>            Priority: P2
>             Fix For: 2.22.0
>
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> After BEAM-9383, Dataflow specific jars (dataflow-worker.jar, windmill_main) could be overwritten when two or more jobs share the same staging location. Since they 1) should have specific predefined names AND 2) should have unique location for avoiding collision, they need special handling when staging artifacts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)