hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Navis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-6437) DefaultHiveAuthorizationProvider should not initialize a new HiveConf
Date Fri, 25 Jul 2014 05:32:38 GMT

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

Navis updated HIVE-6437:
------------------------

    Attachment: HIVE-6437.2.patch.txt

Changed to reconnect automatically on any meta conf changes, removing test only configuration
"hive.metastore.force.reload.conf"

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

Mime
View raw message