[
https://issues.apache.org/jira/browse/FLINK-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103867#comment-14103867
]
Stephan Ewen commented on FLINK-954:
------------------------------------
I merged the pull request https://github.com/apache/incubator-flink/pull/82
Nice job so far, I especially like the zoom :-)
Here are a few more suggestions.
- Setting the ship strategy of a broadcast variable from "broadcast" to
"broadcast variable" would make it better understandable.
- I think a linebreak in the channel labels (between shipstrategy / local
strategy / dam mode) would help the readability
- Some nodes can be at the same time "next partial solution" and "termination
criterion", or "next workset" and "solution set delta". It currently seems to
highlight one one of them.
- Is there some way to draw a feedback arrow from the next partial solution
to the partial solution?
- Ultimately, it may make sense to not use a nested canvas for the iteration,
but to unnest the data flow and draw everything on the same canvas. Then we
would not need the "mirror of" boxes.
> Improvements to the Web Frontend Plan presentation
> --------------------------------------------------
>
> Key: FLINK-954
> URL: https://issues.apache.org/jira/browse/FLINK-954
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Affects Versions: 0.6-incubating
> Reporter: Stephan Ewen
> Assignee: Jonathan Hasenburg
> Priority: Minor
>
> I propose some changes to the way the plan is displayed in the webfrontend:
> 1. Add zoom buttons (+/-). On Laptops where you have no mouse wheel, you
> cannot zoom the graph.
> 2. Omit the ID in the title of the operators (maybe list it in the bottom)
> 3. Rename "Driver Strategy" to "Strategy" or "Operations"
> 4. Make the arrows from Broadcast variables enter the box from top/bottom,
> rather than from the left.
> 5. Instead of writing in a node "Additional Edge to Node X" , can you
> actually draw a box X and have an arrow from X to that node?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
