[
https://issues.apache.org/jira/browse/BEAM-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839880#comment-15839880
]
Luke Cwik commented on BEAM-1325:
---------------------------------
We can recursively look at the "Class-Path" manifest of each jar, seeded from
the jars of the initial class path used to launch java.
We would need to be able to upload all these files to GCS and back to the
worker rewriting the "Class-Path" manifests with the new paths.
> 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
> Assignee: Davor Bonaci
>
> 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.4#6332)
