[
https://issues.apache.org/jira/browse/BEAM-9383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116879#comment-17116879
]
Steve Niemitz commented on BEAM-9383:
-------------------------------------
{quote}Steve, why would two workers jars be staged at the same location ?
{quote}
Job A runs with `--dataflowWorkerJar=myjar1.jar`, staging path =
`gs://somebucket/`, the jar gets uploaded as
`gs://somebucket/dataflow-worker.jar`.
Job B runs with `–dataflowWorkerJar=myjar2.jar`, same staging path, the jar is
uploaded as gs://somebucket/dataflow-worker.jar and overwrites the one from Job
A. Previously, the first jar would have been uploaded as
gs://somebucket/myjar1-<hash>.jar, and the second as
gs://somebucket/myjar2-<hash>.jar, so the names wouldn't collide.
{quote}Also, I'm not sure why we started picking up new jars from JRE libraries
for staging
{quote}
I think this might actually have been unrelated to this change, even after
reverting the commit I'm still seeing some "bonus" jars get 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)
