You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@druid.apache.org by Clint Wylie <cl...@imply.io> on 2019/11/11 21:30:12 UTC
replacing the old web consoles
Hi all,
Vadim and I have been working on a PR to replace and remove all of the old
coordinator and overlord web consoles with the new web console that is
currently only served from the router. The new console will operate with
the subset of functionality which is appropriate to each service type. This
new ui will be functionally equivalent to what was available, with the
exception of the segment timeline that is available on the newer old
coordinator console, which I believe Vad plans to add in a follow-up (there
is already a version of this on the new router web console). We think this
will give users a more consistent and coherent experience when operating
Druid, and it removes a rather large chunk of code from the code-base which
should make maintenance a lot easier on our end.
You can find the PR here:
https://github.com/apache/incubator-druid/pull/8838. We think this PR is
ready to merge, but wanted to ask the list if anyone has any concerns
before we move forward with this.
Cheers,
Clint
Re: replacing the old web consoles
Posted by Himanshu <g....@gmail.com>.
Thanks Clint and Vadim for the work. It is great for the users like me who
haven't gotten around to using routers yet and use the older consoles.
> exception of the segment timeline that is available on the newer old
coordinator console, which I believe Vad plans to add in a follow-up
I do find segment timeline useful on the coordinator console, so it would
be great if follow-up work shows up sometime before next Druid release.
On Mon, Nov 11, 2019 at 3:42 PM Vadim Ogievetsky <vo...@apache.org>
wrote:
> Thanks for posting Clint!
>
> I wanted to add that all the code being removed is totally unmaintained
> (and has been for a while), has many errors that show up in the JS console,
> and depends on old libraries marked with vulnerabilities.
>
> This is the main motivation to actually remove the old consoles as opposed
> to just hiding them but letting them live as is.
>
> On 2019/11/11 21:30:12, Clint Wylie <cl...@imply.io> wrote:
> > Hi all,
> >
> > Vadim and I have been working on a PR to replace and remove all of the
> old
> > coordinator and overlord web consoles with the new web console that is
> > currently only served from the router. The new console will operate with
> > the subset of functionality which is appropriate to each service type.
> This
> > new ui will be functionally equivalent to what was available, with the
> > exception of the segment timeline that is available on the newer old
> > coordinator console, which I believe Vad plans to add in a follow-up
> (there
> > is already a version of this on the new router web console). We think
> this
> > will give users a more consistent and coherent experience when operating
> > Druid, and it removes a rather large chunk of code from the code-base
> which
> > should make maintenance a lot easier on our end.
> >
> > You can find the PR here:
> > https://github.com/apache/incubator-druid/pull/8838. We think this PR is
> > ready to merge, but wanted to ask the list if anyone has any concerns
> > before we move forward with this.
> >
> > Cheers,
> > Clint
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@druid.apache.org
> For additional commands, e-mail: dev-help@druid.apache.org
>
>
Re: replacing the old web consoles
Posted by Vadim Ogievetsky <vo...@apache.org>.
Thanks for posting Clint!
I wanted to add that all the code being removed is totally unmaintained (and has been for a while), has many errors that show up in the JS console, and depends on old libraries marked with vulnerabilities.
This is the main motivation to actually remove the old consoles as opposed to just hiding them but letting them live as is.
On 2019/11/11 21:30:12, Clint Wylie <cl...@imply.io> wrote:
> Hi all,
>
> Vadim and I have been working on a PR to replace and remove all of the old
> coordinator and overlord web consoles with the new web console that is
> currently only served from the router. The new console will operate with
> the subset of functionality which is appropriate to each service type. This
> new ui will be functionally equivalent to what was available, with the
> exception of the segment timeline that is available on the newer old
> coordinator console, which I believe Vad plans to add in a follow-up (there
> is already a version of this on the new router web console). We think this
> will give users a more consistent and coherent experience when operating
> Druid, and it removes a rather large chunk of code from the code-base which
> should make maintenance a lot easier on our end.
>
> You can find the PR here:
> https://github.com/apache/incubator-druid/pull/8838. We think this PR is
> ready to merge, but wanted to ask the list if anyone has any concerns
> before we move forward with this.
>
> Cheers,
> Clint
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@druid.apache.org
For additional commands, e-mail: dev-help@druid.apache.org
Re: replacing the old web consoles
Posted by Vadim Ogievetsky <vo...@apache.org>.
Hi All,
Firstly: I have just added the segment timeline to the coordinator version of the console https://github.com/apache/incubator-druid/pull/8838/commits/ef6f8efb23b66be5a70e6f53138509cc30ee540f
This now makes the coordinator version of the console a complete functional replacement for the legacy console.
David, the UX goes as follows:
After this change the Router, Coordiantor, and Overlord all serve the exact same JS asset. When the console loads it does a capability check by trying to query certain APIs.
Specifically it checks for:
- SQL query-ability (for system tables)
- Native query-ability
- Cooridnator API availability (directly or via management proxy)
- Overlord API availability (directly or via management proxy)
It then goes into an appropriate mode depending on what capabilities it has access to.
On the Coordinator it will not have access to the query aspects and will go into a restricted mode where some features are disabled. This restricted mode is still functionally equivalent/superior to the old coordinator console. You will still get the most complete experience with the console when it is served from the Router as it is the only node that offers all those APIs.
In the future (not part of 0.17.0 release) it would be nice to have the console served on the Broker also and put the management proxy into the Broker so it can also offer the complete experience.
On 2019/11/12 02:44:47, David Glasser <gl...@apollographql.com> wrote:
> The idea here is that you would be able to get the equivalent experience of
> the new web console without running a router?
>
> If you are still running separate coordinator and overlord, what does the
> user experience feel like here? Do you have two separate "half" apps that
> you have to bookmark and switch between manually, or do they both serve the
> same React app but just talk to two different backends?
>
> On Mon, Nov 11, 2019 at 1:30 PM Clint Wylie <cl...@imply.io> wrote:
>
> > Hi all,
> >
> > Vadim and I have been working on a PR to replace and remove all of the old
> > coordinator and overlord web consoles with the new web console that is
> > currently only served from the router. The new console will operate with
> > the subset of functionality which is appropriate to each service type. This
> > new ui will be functionally equivalent to what was available, with the
> > exception of the segment timeline that is available on the newer old
> > coordinator console, which I believe Vad plans to add in a follow-up (there
> > is already a version of this on the new router web console). We think this
> > will give users a more consistent and coherent experience when operating
> > Druid, and it removes a rather large chunk of code from the code-base which
> > should make maintenance a lot easier on our end.
> >
> > You can find the PR here:
> > https://github.com/apache/incubator-druid/pull/8838. We think this PR is
> > ready to merge, but wanted to ask the list if anyone has any concerns
> > before we move forward with this.
> >
> > Cheers,
> > Clint
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@druid.apache.org
For additional commands, e-mail: dev-help@druid.apache.org
Re: replacing the old web consoles
Posted by David Glasser <gl...@apollographql.com>.
The idea here is that you would be able to get the equivalent experience of
the new web console without running a router?
If you are still running separate coordinator and overlord, what does the
user experience feel like here? Do you have two separate "half" apps that
you have to bookmark and switch between manually, or do they both serve the
same React app but just talk to two different backends?
On Mon, Nov 11, 2019 at 1:30 PM Clint Wylie <cl...@imply.io> wrote:
> Hi all,
>
> Vadim and I have been working on a PR to replace and remove all of the old
> coordinator and overlord web consoles with the new web console that is
> currently only served from the router. The new console will operate with
> the subset of functionality which is appropriate to each service type. This
> new ui will be functionally equivalent to what was available, with the
> exception of the segment timeline that is available on the newer old
> coordinator console, which I believe Vad plans to add in a follow-up (there
> is already a version of this on the new router web console). We think this
> will give users a more consistent and coherent experience when operating
> Druid, and it removes a rather large chunk of code from the code-base which
> should make maintenance a lot easier on our end.
>
> You can find the PR here:
> https://github.com/apache/incubator-druid/pull/8838. We think this PR is
> ready to merge, but wanted to ask the list if anyone has any concerns
> before we move forward with this.
>
> Cheers,
> Clint
>