I think that it is important to have a nice "official" (or at least free) Flink UI, we use it to see the detail of the jobs. It's very useful for people starting working with Flink and also for those that does not have the resources to write a custom UI. How are you going to monitor the status of a job otherwise??
On Wed, Oct 31, 2018 at 8:48 AM Fabian Wollert <fab...@zalando.de> wrote: > Hi Till, I basically agree with all your points. i would stress the > "dustiness" of the current architecture: the package manager used (bower) > is deprecated since a long time, the chance for the builds of the flink web > dashboard not working anymore is increasing every day. > > About the knowledge in the community: Two days is not a lot of time, but > interest in this topic seems to be minor anyways. Is someone using the > Flink Web Dashboard at all, or is everyone running their own custom > solutions? Because if there is no interest in using the Web UI AND no one > interested in developing, there would be no need to package this as part of > the official Flink package, but rather develop an independent solution (I'm > not voting for this right now, just putting it out), if at all. The > official package could then just ship with the API, which other solutions > can build upon. This solution could be from an agile point of view also the > best (enhanced testing, independent and more effective dev workflow, etc.), > but is bad for the usage of the Flink UI, because people need to install > two things individually (Flink and the web dashboard). > > How did the choice for Angular1 happen back then? Who was writing the > Dashboard in the first place? > > Cheers > > -- > > > *Fabian WollertZalando SE* > > E-Mail: fab...@zalando.de > > > Am Di., 30. Okt. 2018 um 15:07 Uhr schrieb Till Rohrmann < > trohrm...@apache.org>: > > > Thanks for starting this discussion Fabian! I think our web UI technology > > stack is quite dusty by now and it would be beneficial to think about its > > technological future. > > > > On the one hand, our current web UI works more or less reliable and > > changing the underlying technology has the risk of breaking things. > > Moreover, there might be the risk that the newly chosen technology will > be > > deprecated at some point in time as well. > > > > On the other hand, we don't have much Angular 1 knowledge in the > community > > and extending the web UI is, thus, quite hard at the moment. Maybe by > using > > some newer web technologies we might be able to attract more people with > a > > web technology background to join the community. > > > > The lack of people working on the web UI is for me the biggest problem I > > would like to address. If there is interest in the web UI, then I'm quite > > sure that we will be able to even migrate to some other technology in the > > future. The next important issue for me is to do the change incrementally > > if possible. Ideally we never break the web UI in the process of > migrating > > to a new technology. I'm not an expert here so it might or might not be > > possible. But if it is, then we should design the implementation steps in > > such a way. > > > > Cheers, > > Till > > > > On Mon, Oct 29, 2018 at 1:06 PM Fabian Wollert <fab...@zalando.de> > wrote: > > > > > Hi everyone, > > > > > > in this email thread > > > < > > > > > > http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Flink-Cluster-Overview-Dashboard-Improvement-Proposal-td24531.html > > > > > > > and the tickets FLINK-10705 > > > <https://issues.apache.org/jira/browse/FLINK-10705> and FLINK-10706 > > > <https://issues.apache.org/jira/browse/FLINK-10706> the discussion > came > > up > > > whether to change the underlying architecture of Flink's Web Dashboard > > from > > > Angular1 to something else. This email thread should be solely to > discuss > > > the pro's and con's of this, and what could be the target architecture. > > > > > > My choice would be React. Personally I agree with Till's comments in > the > > > ticket, Angular 1 being basically outdated and is not having a large > > > following anymore. From my experience the choice between Angular 2-7 or > > > React is subjective, you can get things done with both. I personally > only > > > have experience with React, so I personally would be faster to develop > > > with this one. I currently have not planned to learn Angular as well > > (being > > > a more backend focused developer in general) so if the decision would > be > > to > > > go with Angular, i would be unfortunately out of this rework of the > Flink > > > Dashboard most certainly. > > > > > > Additionally i would like to get rid of bower, since its officially > > > deprecated <https://bower.io/blog/2017/how-to-migrate-away-from-bower/ > >. > > > my > > > idea would be to just use a create-react-app package with npm and > webpack > > > under the hood. no need for additional lib's here imho. But again: > thats > > > mostly what i've been working with recently, so thats a subjective > > point. I > > > could imagine getting used to yarn in the future as well. > > > > > > Cheers > > > Fabian > > > > > > -- > > > > > > > > > *Fabian WollertZalando SE* > > > > > > E-Mail: fab...@zalando.de > > > > > >
