[
https://issues.apache.org/jira/browse/BEAM-8016?focusedWorklogId=345698&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-345698
]
ASF GitHub Bot logged work on BEAM-8016:
----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Nov/19 00:21
Start Date: 19/Nov/19 00:21
Worklog Time Spent: 10m
Work Description: qinyeli commented on issue #10132: [BEAM-8016] Pipeline
Graph
URL: https://github.com/apache/beam/pull/10132#issuecomment-555272354
Thanks Ning! I haven't been catching up with the latest changes in
Interactive Beam, so consider my comments as from someone with somewhat context
but not all. A lot of my comments are "This is not very obvious, can you
elaborate?"
So it looks good in general. Some comments in line. Also a couple of
questions out of curiosity.
* Are we getting rid of the tooltips displaying the intermediate results? Do
they not fit in the new model?
* What do the PCollections look like if the user did not specify the
PCollection name as a variable?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 345698)
Time Spent: 1h 20m (was: 1h 10m)
> Render Beam Pipeline as DOT with Interactive Beam
> ---------------------------------------------------
>
> Key: BEAM-8016
> URL: https://issues.apache.org/jira/browse/BEAM-8016
> Project: Beam
> Issue Type: Improvement
> Components: runner-py-interactive
> Reporter: Ning Kang
> Assignee: Ning Kang
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> With work in https://issues.apache.org/jira/browse/BEAM-7760, Beam pipeline
> converted to DOT then rendered should mark user defined variables on edges.
> With work in https://issues.apache.org/jira/browse/BEAM-7926, it might be
> redundant or confusing to render arbitrary random sample PCollection data on
> edges.
> We'll also make sure edges in the graph corresponds to output -> input
> relationship in the user defined pipeline. Each edge is one output. If
> multiple down stream inputs take the same output, it should be rendered as
> one edge diverging into two instead of two edges.
> For advanced interactivity highlight where each execution highlights the part
> of the pipeline really executed from the original pipeline, we'll also
> provide the support in beta.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
