[ https://issues.apache.org/jira/browse/BEAM-5859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maximilian Michels updated BEAM-5859: ------------------------------------- Attachment: wordcount.png > 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 > > > 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: > !image-2018-10-25-19-33-48-626.png! > TFX: > !image-2018-10-25-19-23-04-301.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)