[ 
https://issues.apache.org/jira/browse/HIVE-27169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pravin Sinha resolved HIVE-27169.
---------------------------------
    Resolution: Fixed

> 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: 1h
>  Remaining Estimate: 0h
>
> _*AIM*_
> Create a new locked list called _*hive.conf.locked.list*_ which contains 
> comma separated configuration that can't be changed during runtime. If 
> someone try to change them at runtime then it will give WARN log on beeline 
> itself and will not change that config.
>  
> _*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 will be very helpful when organisations are migrating from Hive 1.x, 
> Hive2.x to higher version and admin want to enforce some configuration which 
> should remain constant.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to