John Omernik created DRILL-4619:
-----------------------------------
Summary: Provide bootstrap-cluster-options.json functionality
similar to bootstrap-storage-plugins
Key: DRILL-4619
URL: https://issues.apache.org/jira/browse/DRILL-4619
Project: Apache Drill
Issue Type: Wish
Components: Server
Affects Versions: 1.6.0
Reporter: John Omernik
Per https://drill.apache.org/docs/plugin-configuration-basics/
bootstrap-storage-plugins.json is a file that allows administrators to provide
a base storage plugin configuration on instantiation of a new cluster. This
file is only created on the first initialization of a drill cluster, and per
the documentation is ignored. (This allows you to create an initial set of
storage plugins, and then alter them without having them clobbered by the
bootstrap file).
This JIRA is about adding a "bootstrap-cluster-options.json" file that can
provide a similar capability, but instead of creating storage plugins, sets any
cluster wide settings, once. Basically, if this file exists in the class path,
then on registration into Zookeeper, any settings specified in this file will
be updated in the master cluster settings.
Like the storage-plugin feature, after the cluster is initialized, this file
has no more use, and is ignored on all future drillbit startups (so that
settings changed manually don't get changed). There are many uses for this
* Enabling and configuring Multi-tenancy on a new Drill Cluster
* Configuring Default Resource Manager options for your Cluster
* Changing defaults on storage plugin options
* json read options etc
* Parquet options
* etc
* Configuring admin users or groups for your drill cluster
* Updating cluster defaults for compression, storage format etc
* Many more
The implementation should be similar to the storage plugin, and I am guessing
should use HOCON similar to the drill-override for consistency in naming.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
