You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/03/23 19:06:00 UTC

[jira] [Work logged] (HIVE-27169) New Locked List to prevent configuration change at runtime without throwing error

     [ https://issues.apache.org/jira/browse/HIVE-27169?focusedWorklogId=852675&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-852675 ]

ASF GitHub Bot logged work on HIVE-27169:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Mar/23 19:05
            Start Date: 23/Mar/23 19:05
    Worklog Time Spent: 10m 
      Work Description: Aggarwal-Raghav opened a new pull request, #4146:
URL: https://github.com/apache/hive/pull/4146

   ### What changes were proposed in this pull request?
   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.
   
   
   ### Why are the changes needed?
   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 hive 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 hive scripts.
   
   
   ### Does this PR introduce _any_ user-facing change?
   This config can be documented.
   
   ### How was this patch tested?
   On a cluster
   




Issue Time Tracking
-------------------

            Worklog Id:     (was: 852675)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>          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)