Github user sohami commented on the issue:
https://github.com/apache/drill/pull/870
@ppadma -
1) For the ease of use. Once the security is being configured for Drill
then it's better if all the config changes are done in single place (which is
drill-override.conf) and then make sure that all communications are secure.
With this option user doesn't have to explicitly go and edit the Storage Plugin
configuration to enable security.
2) It will take care of enabling/disabling security both for active and
inactive plugins.
3) This can be extended for handling security of all the storage plugin.
Hence this config can be a single place to enable/disable security for all the
plugins in one go rather than doing it manually for each and every plugin one
by one.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
