[
https://issues.apache.org/jira/browse/FLINK-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802706#comment-14802706
]
ASF GitHub Bot commented on FLINK-2357:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1139#issuecomment-141035389
Yes, the values you refer to are still placeholders.
I would like to merge this in its current state and improve on it in the
master branch. The old frontend is still the default, and this one has to be
explicitly activated, to there should be no conflict.
> New JobManager Runtime Web Frontend
> -----------------------------------
>
> Key: FLINK-2357
> URL: https://issues.apache.org/jira/browse/FLINK-2357
> Project: Flink
> Issue Type: New Feature
> Components: Webfrontend
> Affects Versions: 0.10
> Reporter: Stephan Ewen
> Attachments: Webfrontend Mockup.pdf
>
>
> We need to improve rework the Job Manager Web Frontend.
> The current web frontend is limited and has a lot of design issues
> - It does not display and progress while operators are running. This is
> especially problematic for streaming jobs
> - It has no graph representation of the data flows
> - it does not allow to look into execution attempts
> - it has no hook to deal with the upcoming live accumulators
> - The architecture is not very modular/extensible
> I propose to add a new JobManager web frontend:
> - Based on Netty HTTP (very lightweight)
> - Using rest-style URLs for jobs and vertices
> - integrating the D3 graph renderer of the previews with the runtime monitor
> - with details on execution attempts
> - first class visualization of records processed and bytes processed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
