[GitHub] [beam] kennknowles opened a new issue, #19218: Improve Traceability of Pipeline translation

[GitBox <gi...@apache.org>]

kennknowles opened a new issue, #19218:
URL: https://github.com/apache/beam/issues/19218

   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
   
    
   
   Imported from Jira [BEAM-5859](https://issues.apache.org/jira/browse/BEAM-5859). Original Jira may contain additional context.
   Reported by: mxm.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org