[
https://issues.apache.org/jira/browse/HIVE-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HIVE-6437:
--------------------------
Assignee: (was: Harsh J)
This appears to be done cause {{Hive#get(…)}} expects a HiveConf parameter and
not a Configuration one.
I don't see {{Hive#get(…)}} particularly relying on a HiveConf specific method,
but since the change is deeper than what I envisioned earlier, I'll leave it to
the more knowledgeable folks to decide here.
> 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
> Priority: Trivial
>
> 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.1.5#6160)
