[
https://issues.apache.org/jira/browse/HIVE-27169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HIVE-27169:
----------------------------------
Labels: pull-request-available (was: )
> New Locked List to prevent configuration change at runtime without throwing
> error
> ---------------------------------------------------------------------------------
>
> Key: HIVE-27169
> URL: https://issues.apache.org/jira/browse/HIVE-27169
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 4.0.0-alpha-2
> Reporter: Raghav Aggarwal
> Assignee: Raghav Aggarwal
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> _*AIM*_
> Create a new locked list called{{ hive.conf.locked.list}} which contains
> comma separated configuration that won't be changed during runtime. If
> someone try to change them at runtime then it will give WARN log on beeline
> itself.
>
> _*How is it different from Restricted List?*_
> When running hql file or at runtime, if a configuration present in restricted
> list get updated then it will throw error and won't proceed with further
> execution of hql file.
> With locked list, the configuration that is getting updated will throw WARN
> log on beeline and will continue to execute the hql file.
>
> _*Why is it required?*_
> In organisations, admin want to enforce some configs which user shouldn't be
> able to change at runtime and it shouldn't affect user's existing hql
> scripts. Therefore, this locked list will be useful as it will not allow user
> to change the value of particular configs and it will also not stop the
> execution of hql scripts.
>
> {_}*NOTE*{_}: Only at cluster level {{hive.conf.locked.list }}can be set and
> after that the hive service needs to be restarted.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
