[
https://issues.apache.org/jira/browse/HIVE-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075924#comment-14075924
]
Lefty Leverenz commented on HIVE-6437:
--------------------------------------
*hive.metastore.force.reload.conf* was introduced in Hive 0.6.0 (default false)
but isn't documented in the wiki. Even though it's going to be removed, it
should probably be documented with version information -- I suggest the Test
Properties section, not the Metastore section even though it's a
hive.metastore.* property.
* [Configuration Properties -- Test Properties |
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-TestProperties]
* [Configuration Properties -- Metastore |
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-MetaStore]
> 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
> Attachments: HIVE-6437.1.patch.txt, HIVE-6437.2.patch.txt,
> HIVE-6437.3.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.2#6252)
