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

Posted to commits@beam.apache.org by "Thomas Groh (JIRA)" <ji...@apache.org> on 2018/05/23 00:40:00 UTC

[jira] [Created] (BEAM-4384) Load in-process FnHarness instances with a restricted classpath

Thomas Groh created BEAM-4384:
---------------------------------

             Summary: 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


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
(v7.6.3#76005)