You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2017/03/30 16:50:41 UTC

[jira] [Assigned] (BEAM-1325) DataflowRunner support for Class-Path jars

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

Daniel Halperin reassigned BEAM-1325:
-------------------------------------

    Assignee:     (was: Davor Bonaci)

> DataflowRunner support for Class-Path jars
> ------------------------------------------
>
>                 Key: BEAM-1325
>                 URL: https://issues.apache.org/jira/browse/BEAM-1325
>             Project: Beam
>          Issue Type: New Feature
>          Components: runner-dataflow
>            Reporter: Daniel Halperin
>
> See https://github.com/GoogleCloudPlatform/DataflowJavaSDK/issues/538
> The code that infers {{--filesToStage}} from the classpath does not seem to support a classpath jar. which uses a {{Class-Path}} manifest to indicate which other jars are needed at runtime. This is apparently a standard, approved way to pass the classpath.
> We need to add this support to {{DataflowRunner#detectClasspathResourcesToStage}}, but correctly representing the user's classpath continues to be challenging.
> (As {{FlinkRunner}} has copied this code, we should probably either pull the common utility somewhere public or update the FlinkRunner too?)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)