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

Vaibhav Gumashta updated HIVE-5359:
-----------------------------------

    Description: When HS2 is brought up, the server can be inited with the 
given hive config: HiveServer2#init(HiveConf hiveConf). That configuration 
should be applied through the entire setup process for all services. However, 
while starting ThriftCLIService, it creates a new HiveAuthFactory object, whose 
constructor creates a new HiveConf object and ends up using it rather than 
using the HiveConf passed during HS2 bootstrap.  (was: When HS2 is brought up, 
the server can be inited with the given hive config: HiveServer2#init(HiveConf 
hiveConf). That configuration should be applied through the entire setup 
process for all services. However, while starting ThriftBinaryCLIService, it 
creates a new HiveAuthFactory object, whose constructor creates a new HiveConf 
object and ends up using it rather than using the HiveConf passed during HS2 
bootstrap.)
    
> HiveAuthFactory does not honor the hive configuration passed while creating 
> HiveServer2
> ---------------------------------------------------------------------------------------
>
>                 Key: HIVE-5359
>                 URL: https://issues.apache.org/jira/browse/HIVE-5359
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>
> When HS2 is brought up, the server can be inited with the given hive config: 
> HiveServer2#init(HiveConf hiveConf). That configuration should be applied 
> through the entire setup process for all services. However, while starting 
> ThriftCLIService, it creates a new HiveAuthFactory object, whose constructor 
> creates a new HiveConf object and ends up using it rather than using the 
> HiveConf passed during HS2 bootstrap.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to