gianm commented on issue #8150: Make the Unified web console available on Coordinator URL: https://github.com/apache/incubator-druid/issues/8150#issuecomment-524478504 > @gianm @vogievetsky does Imply has any plans to implement part 2 of #6923? I would definitely like to make it available outside of just the Router. The tricky bit is that the unified console uses Coordinator APIs, Overlord APIs, and Broker APIs. It currently runs on the Router because that is the only process type that can make all three kinds of APIs available (it proxies to them all). I think one of the following plans might make the most sense, 1. Do it on the Coordinator, perhaps by falling back to a 'light' mode that only uses Coordinator and Overlord APIs. Not all functionality would be available. In particular, query functionality would not be available, as well as anything that relies on [system tables](https://druid.apache.org/docs/latest/querying/sql#system-schema). 2. Do it on the Broker, perhaps by folding Router functionality into the Broker (`druid.broker.asRouter = true`?). This would allow the Broker to proxy to the Coordinator and Overlord APIs. When I think about this right now I lean to the second idea (Broker) since it promotes the idea of a single server type that you use to interact with your Druid cluster. It feels like a simpler experience for especially new users.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@druid.apache.org For additional commands, e-mail: commits-h...@druid.apache.org
