You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/05/27 03:36:00 UTC
[jira] [Work logged] (BEAM-10078) uniquify Dataflow specific jars
when staging
[ https://issues.apache.org/jira/browse/BEAM-10078?focusedWorklogId=437330&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-437330 ]
ASF GitHub Bot logged work on BEAM-10078:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 27/May/20 03:35
Start Date: 27/May/20 03:35
Worklog Time Spent: 10m
Work Description: chamikaramj commented on pull request #11814:
URL: https://github.com/apache/beam/pull/11814#issuecomment-634085087
Did you mean review https://github.com/apache/beam/pull/11813 and not this one ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 437330)
Remaining Estimate: 0h
Time Spent: 10m
> uniquify Dataflow specific jars when staging
> --------------------------------------------
>
> Key: BEAM-10078
> URL: https://issues.apache.org/jira/browse/BEAM-10078
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Heejong Lee
> Assignee: Heejong Lee
> Priority: P2
> Fix For: 2.22.0
>
> Time Spent: 10m
> 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)