hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-6437) DefaultHiveAuthorizationProvider should not initialize a new HiveConf
Date Wed, 30 Jul 2014 14:55:40 GMT


Hive QA commented on HIVE-6437:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 5838 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed

This message is automatically generated.


> DefaultHiveAuthorizationProvider should not initialize a new HiveConf
> ---------------------------------------------------------------------
>                 Key: HIVE-6437
>                 URL:
>             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,
HIVE-6437.4.patch.txt, HIVE-6437.5.patch.txt, HIVE-6437.6.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

View raw message