[
https://issues.apache.org/jira/browse/HIVE-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121017#comment-14121017
]
Venki Korukanti commented on HIVE-6245:
---------------------------------------
[~thejas] Sorry about that. I see in all Hive QA runs where the test failed,
second connection is failed to establish. There isn't any info in hive.log to
narrow down. I will try to repro locally and update (HIVE-7942 is created for
tracking).
> HS2 creates DBs/Tables with wrong ownership when HMS setugi is true
> -------------------------------------------------------------------
>
> Key: HIVE-6245
> URL: https://issues.apache.org/jira/browse/HIVE-6245
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 0.12.0, 0.13.0
> Reporter: Chaoyu Tang
> Assignee: Venki Korukanti
> Fix For: 0.14.0
>
> Attachments: HIVE-6245.2.patch.txt, HIVE-6245.3.patch.txt,
> HIVE-6245.4.patch, HIVE-6245.5.patch, HIVE-6245.patch
>
>
> The case with following settings is valid but does not work correctly in
> current HS2:
> ==
> hive.server2.authentication=NONE (or LDAP)
> hive.server2.enable.doAs= true
> hive.metastore.sasl.enabled=false
> hive.metastore.execute.setugi=true
> ==
> Ideally, HS2 is able to impersonate the logged in user (from Beeline, or JDBC
> application) and create DBs/Tables with user's ownership.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
