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/26 15:47:00 UTC

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

    [ https://issues.apache.org/jira/browse/BEAM-10078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116836#comment-17116836 ] 

Brian Hulette commented on BEAM-10078:
--------------------------------------

[~heejong] should this be blocking 2.22? Based on the questions from https://beam.apache.org/contribute/release-guide/#review-cherry-picks I think this is related to a new feature, and thus should wait for the next release. But maybe I'm mistaken?

> 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
>
>
> Dataflow specific jars (dataflow-worker.jar, windmill_main) need special handling when staging.



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