Re: [DISCUSS] Change underlying Frontend Architecture for Flink Web Dashboard

think about deprecating the old web UI and eventually to drop it. Of > > course, initially we should give it a thorough review. > > > > Cheers, > > Till > > > > On Mon, Nov 5, 2018 at 8:40 AM Fabian Wollert wrote: > > > > > Hi Yadong, this is awesome,

Re: [DISCUSS] Change underlying Frontend Architecture for Flink Web Dashboard

ing please let me know. Look forward to your feedback and > suggestions soon. > > Best regards > Yadong > > > On Fri, Nov 2, 2018 at 5:28 PM Fabian Wollert wrote: > > > Hi Yadong, this looks awesome. is there any chance you can already share > > the code of the new

Re: [DISCUSS] Change underlying Frontend Architecture for Flink Web Dashboard

d in a timely manner / not at all, which mind you > > >> > applies to virtually all components. This also won't change by > moving > > it > > >> > out of Flink. > > >> > > > >> > Having it in Flink also guarantees that there is an >

Re: [DISCUSS] Change underlying Frontend Architecture for Flink Web Dashboard

the implementation steps in > such a way. > > Cheers, > Till > > On Mon, Oct 29, 2018 at 1:06 PM Fabian Wollert wrote: > > > Hi everyone, > > > > in this email thread > > < > > > http://apache-flink-mailing-list-archive.1008284.n

[DISCUSS] Change underlying Frontend Architecture for Flink Web Dashboard

Hi everyone, in this email thread and the tickets FLINK-10705 and FLINK-10706

Re: [DISCUSS] Flink Cluster Overview Dashboard Improvement Proposal

ge is purely about the > layout of the WebUI. > > On 29.10.2018 12:39, Fabian Wollert wrote: > > Hi again, > > > > Chesnay correctly commented in the tickets that we first should discuss > > here, if changing the underlying technology for the Flink Web Dashboard > is &

Re: [DISCUSS] Flink Cluster Overview Dashboard Improvement Proposal

. 2018 um 09:21 Uhr schrieb Fabian Wollert : > Hi everyone, > > thx for all the feedback. I created now > https://issues.apache.org/jira/browse/FLINK-10705 with sub tickets to > tackle this. i also found some time this weekend and implemented the first > draft, which i will post in th

Re: [DISCUSS] Flink Cluster Overview Dashboard Improvement Proposal

-Mail: fab...@zalando.de Am Sa., 27. Okt. 2018 um 17:15 Uhr schrieb Robert Metzger < rmetz...@apache.org>: > Hey, > Sorry for the delay. > > Yes -- I would be open to revisit the underlying technologies. > > Best, > Robert > > On Wed, Oct 10, 2018 at 11:28 AM Fabian

[jira] [Created] (FLINK-10707) Improve Cluster Overview in Flink Dashboard

Fabian Wollert created FLINK-10707: -- Summary: Improve Cluster Overview in Flink Dashboard Key: FLINK-10707 URL: https://issues.apache.org/jira/browse/FLINK-10707 Project: Flink Issue Type

[jira] [Created] (FLINK-10706) Rewrite Flink Dashboard with React

Fabian Wollert created FLINK-10706: -- Summary: Rewrite Flink Dashboard with React Key: FLINK-10706 URL: https://issues.apache.org/jira/browse/FLINK-10706 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-10705) Rework Flink Web Dashboard

Fabian Wollert created FLINK-10705: -- Summary: Rework Flink Web Dashboard Key: FLINK-10705 URL: https://issues.apache.org/jira/browse/FLINK-10705 Project: Flink Issue Type: Improvement

Re: [DISCUSS] Flink Cluster Overview Dashboard Improvement Proposal

Hi everyone, thx for all the comments and feedback. Let me address everything individually: @Till: yes, for the start my plan would be to just touch the flink-runtime-web/web-dashboard repo/folder. @Jin Sun: - smaller icons on increasing server counts: yes, thats also something i already

Re: [DISCUSS] Flink Cluster Overview Dashboard Improvement Proposal

Uhr schrieb Fabian Wollert : > Hi everyone, > > disclaimer: i read the contribution guide about improvement requests (i.e. > i should actually just start a jira ticket) but i thought it would make > sense to run this first through the mailing list here. after collecting >

[DISCUSS] Flink Cluster Overview Dashboard Improvement Proposal

Hi everyone, disclaimer: i read the contribution guide about improvement requests (i.e. i should actually just start a jira ticket) but i thought it would make sense to run this first through the mailing list here. after collecting some input i would then create the jira ticket. When accessing

[jira] [Created] (FLINK-5850) implement OAuth 2.0 check in Web Backend API

Fabian Wollert created FLINK-5850: - Summary: implement OAuth 2.0 check in Web Backend API Key: FLINK-5850 URL: https://issues.apache.org/jira/browse/FLINK-5850 Project: Flink Issue Type

[jira] [Created] (FLINK-5848) make Flink Web Backend a little bit more restful

Fabian Wollert created FLINK-5848: - Summary: make Flink Web Backend a little bit more restful Key: FLINK-5848 URL: https://issues.apache.org/jira/browse/FLINK-5848 Project: Flink Issue Type