[jira] [Commented] (HIVE-6437) DefaultHiveAuthorizationProvider should not initialize a new HiveConf

["Lefty Leverenz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596795#comment-15596795 ] 

Lefty Leverenz commented on HIVE-6437:
--------------------------------------

Doc note:  This adds "hive.users.in.admin.role" to the default value of *hive.conf.restricted.list* which was created by HIVE-2935 in release 0.11.0 and changed by HIVE-5953 in 0.13.0.

* [Configuration Properties -- hive.conf.restricted.list | https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-hive.conf.restricted.list]

The default value is changed again by HIVE-13853 (2.1.0) and HIVE-14099 (2.2.0).

> DefaultHiveAuthorizationProvider should not initialize a new HiveConf
> ---------------------------------------------------------------------
>
>                 Key: HIVE-6437
>                 URL: https://issues.apache.org/jira/browse/HIVE-6437
>             Project: Hive
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 0.13.0
>            Reporter: Harsh J
>            Assignee: Navis
>            Priority: Trivial
>             Fix For: 0.14.0
>
>         Attachments: HIVE-6437.1.patch.txt, HIVE-6437.2.patch.txt, HIVE-6437.3.patch.txt, HIVE-6437.4.patch.txt, HIVE-6437.5.patch.txt, HIVE-6437.6.patch.txt, HIVE-6437.7.patch.txt
>
>
> During a HS2 connection, every SessionState got initializes a new DefaultHiveAuthorizationProvider object (on stock configs).
> In turn, DefaultHiveAuthorizationProvider carries a {{new HiveConf(…)}} that may prove too expensive, and unnecessary to do, since SessionState itself sends in a fully applied HiveConf to it in the first place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)