You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Luke Cwik (JIRA)" <ji...@apache.org> on 2018/06/05 18:02:00 UTC
[jira] [Created] (BEAM-4484) Shading model-pipeline /
model-fn-execution / model-job-management produces corrupted classes
Luke Cwik created BEAM-4484:
-------------------------------
Summary: Shading model-pipeline / model-fn-execution / model-job-management produces corrupted classes
Key: BEAM-4484
URL: https://issues.apache.org/jira/browse/BEAM-4484
Project: Beam
Issue Type: Bug
Components: runner-direct
Reporter: Luke Cwik
Assignee: Luke Cwik
During investigation for test failures on [https://github.com/apache/beam/pull/5445,] I discovered that the the post shaded beam-model-pipeline proto filedescriptors were corrupted. It turns out that during the shading process, an over eager string replacement inside a class is corrupting an internal field, in this case it modifies the RunnerApi file descriptor storing
{code:java}
org.apache.beam.model.pipeline.v1.AccumulationMode.Enum{code}
and changing it to
{code:java}
org.apache.beam.repackaged.beam_runners_direct_java.model.pipeline.v1.AccumulationMode.Enum{code}
This problem exists because the proto package name and the java package name collide and use org.apache.beam.model.pipeline.v1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)