[GitHub] [druid] FrankChen021 commented on issue #9926: A Proposal about Extension Center

[GitBox <gi...@apache.org>]

FrankChen021 commented on issue #9926:
URL: https://github.com/apache/druid/issues/9926#issuecomment-635437210


   To introduce Extension Center into druid, I think the first problem needed to solved is to centralize configurations. Extensions don't depend on any configuration files distributed in every node. When user installs an extension, user have to provide required configs and these configs will be saved in the centralized configuration center. Every node read configurations from the center. This solves the 2nd problem mentioned by @suneet-s . 
   
   There're many such solutions to do it. For example, we can use zookeeper to keep configurations and every node listens changes on configuration node to take configuration effect immediately. This is also how Kafka implements dynamic configuration on topics.
   
   As the 1st problem, I think maybe we can divide extensions into two categories, one requires re-start, the other doesn't. Many extensions in my opinion could be installed without a restart, such as emitter extensions, query extensions. For those required a restart, I agree that the restart should left to user. But before restart, Extension Center has done most of arduous work(download/config) to enable an extension.


----------------------------------------------------------------
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org