[
https://issues.apache.org/jira/browse/BEAM-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145582#comment-17145582
]
Beam JIRA Bot commented on BEAM-1325:
-------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14
days. It is now automatically moved to P3. If you are still affected by it, you
can comment and move it back to P2.
> 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: Dan Halperin
> Priority: P3
>
> 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
(v8.3.4#803005)
