[
https://issues.apache.org/jira/browse/BEAM-5859?focusedWorklogId=171619&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-171619
]
ASF GitHub Bot logged work on BEAM-5859:
----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Dec/18 15:40
Start Date: 03/Dec/18 15:40
Worklog Time Spent: 10m
Work Description: mxm commented on a change in pull request #7150:
[BEAM-5859] Improve operator names for portable pipelines
URL: https://github.com/apache/beam/pull/7150#discussion_r238318772
##########
File path:
runners/flink/src/main/java/org/apache/beam/runners/flink/translation/utils/FlinkPipelineTranslatorUtils.java
##########
@@ -77,4 +77,25 @@ public static WindowingStrategy getWindowingStrategy(
e);
}
}
+
+ public static String genOperatorNameFromStagePayload(
Review comment:
Perhaps `ExecutableStageTranslation` would be a good place to put this.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 171619)
Time Spent: 2h (was: 1h 50m)
> Improve Traceability of Pipeline translation
> --------------------------------------------
>
> Key: BEAM-5859
> URL: https://issues.apache.org/jira/browse/BEAM-5859
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
> Reporter: Maximilian Michels
> Priority: Major
> Labels: portability, portability-flink
> Attachments: tfx.png, wordcount.png
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Users often ask how they can reason about the pipeline translation. The Flink
> UI display a confusingly large graph without any trace of the original Beam
> pipeline:
> WordCount:
> !wordcount.png!
> TFX:
> !tfx.png!
> Some aspects which make understanding these graphs hard:
> * Users don't know how the Runner maps Beam to Flink concepts
> * The UI is awfully slow / hangs when the pipeline is reasonable complex
> * The operator names seem to use {{transform.getUniqueName()}} which doesn't
> generate readable name
> * So called Chaining combines operators into a single operator which makes
> understanding which Beam concept belongs to which Flink concept even harder
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
