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

Posted to issues@beam.apache.org by "Kyle Weaver (Jira)" <ji...@apache.org> on 2022/03/03 17:23:00 UTC

[jira] [Updated] (BEAM-13097) Don't assume 1 jar on classpath in portable jar creator

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

Kyle Weaver updated BEAM-13097:
-------------------------------
    Fix Version/s: 2.25.0
         Assignee: Kyle Weaver
       Resolution: Fixed
           Status: Resolved  (was: Open)

> Don't assume 1 jar on classpath in portable jar creator
> -------------------------------------------------------
>
>                 Key: BEAM-13097
>                 URL: https://issues.apache.org/jira/browse/BEAM-13097
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-spark
>            Reporter: Kyle Weaver
>            Assignee: Kyle Weaver
>            Priority: P2
>             Fix For: 2.25.0
>
>
> Right now we assume there is exactly 1 jar, the Spark/Flink job server jar, on the classpath. That assumption is not always correct. We should make this code more flexible, so it works even when there are other jars on the classpath. Perhaps by writing only the specific jar the PortablePipelineJarCreator class came from.
> https://github.com/apache/beam/blob/32dd786f2d6cff02743421c0bb01bd3eea60dbbf/runners/java-job-service/src/main/java/org/apache/beam/runners/jobsubmission/PortablePipelineJarCreator.java#L142



--
This message was sent by Atlassian Jira
(v8.20.1#820001)