[
https://issues.apache.org/jira/browse/BEAM-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17546951#comment-17546951
]
Kenneth Knowles commented on BEAM-4384:
---------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/18762
> Load in-process FnHarness instances with a restricted classpath
> ---------------------------------------------------------------
>
> Key: BEAM-4384
> URL: https://issues.apache.org/jira/browse/BEAM-4384
> Project: Beam
> Issue Type: Improvement
> Components: runner-direct
> Reporter: Thomas Groh
> Priority: P3
>
> The new classpath can contain the Java harness code and the user's classpath.
> This simulates the SDK container, and removes the need for users to provide
> beam-sdks-java-harness as a dependency.
> The idea would be that beam-sdks-java-harness would be a jar containing all
> of its dependencies shaded away similar to what we do for Dataflow. We would
> embed the beam-sdks-java-harness.jar as a jar inside the direct runner jar so
> we wouldn't need to fetch it from Maven and also would be able to solve the
> problem where tests would run from the provided jar.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
