You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2017/10/12 17:25:00 UTC
[jira] [Created] (BEAM-3049) Java SDK Harness bundles non-relocated
code, including Dataflow runner
Kenneth Knowles created BEAM-3049:
-------------------------------------
Summary: Java SDK Harness bundles non-relocated code, including Dataflow runner
Key: BEAM-3049
URL: https://issues.apache.org/jira/browse/BEAM-3049
Project: Beam
Issue Type: Bug
Components: sdk-java-harness
Reporter: Kenneth Knowles
Assignee: Luke Cwik
This causes a problem if something depends on the harness but does not want the harness's copy of its dependencies. I know we intend to break the dependency on the Dataflow runner. It also bundles a couple other things unshaded.
Mostly, the harness should be executed entirely containerized so it doesn't matter, in which case there's no need to relocate anything, and bundling is just a convenience. But we should have a clear policy that we adhere to. Either it is a library and should have good hygeine, or if it doesn't have good hygeine it must not be used as a library.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)