[
https://issues.apache.org/jira/browse/HIVE-18029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263598#comment-16263598
]
Sergey Shelukhin commented on HIVE-18029:
-----------------------------------------
Ok, actually the behavior is more subtle; looks like the argument connection
URL is not handled consistently with the connect command one, and the latter
passes on user name that's entered in the prompt correctly.
So,
{noformat}
!connect (url);user=foo => foo
!connect (url) => whatever is entered in the prompt
beeline -n foo -u (url with or without the user) => foo
beeline -u (url);user=foo => anonymous
beeline -u (url) => anonymous (no prompt)
{noformat}
I'm going to add support for extracting the user from the -u argument, similar
to connect argument
> user mapping - support proper usernames with doAs = false
> ---------------------------------------------------------
>
> Key: HIVE-18029
> URL: https://issues.apache.org/jira/browse/HIVE-18029
> Project: Hive
> Issue Type: Sub-task
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
>
> Right now what happens on unsecure cluster with doAs=false (not sure which
> one is to blame - didn't look into it, maybe both) is {noformat}
> 2017-11-08T21:39:49,404 INFO [HiveServer2-Background-Pool: Thread-205]
> tez.WorkloadManagerFederation: Getting a WM session for anonymous
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
