[
https://issues.apache.org/jira/browse/BEAM-9383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116185#comment-17116185
]
Steve Niemitz commented on BEAM-9383:
-------------------------------------
There's actually another much more serious bug here. If I set a dataflow
worker jar, it gets uploaded to GCS as simply "dataflow-worker.jar". This
means if I have two jobs that have two different worker jars set, they'll
overwrite each other and the last one will win.
The old behavior was correct, the name used was the name of the jar + the
SHA256, just like other classpath elements that were staged.
> Staging Dataflow artifacts from environment
> -------------------------------------------
>
> Key: BEAM-9383
> URL: https://issues.apache.org/jira/browse/BEAM-9383
> Project: Beam
> Issue Type: Sub-task
> Components: java-fn-execution
> Reporter: Heejong Lee
> Assignee: Heejong Lee
> Priority: P2
> Fix For: 2.22.0
>
> Time Spent: 12h
> Remaining Estimate: 0h
>
> Staging Dataflow artifacts from environment
--
This message was sent by Atlassian Jira
(v8.3.4#803005)