[
https://issues.apache.org/jira/browse/HIVE-18029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HIVE-18029:
------------------------------------
Description:
Update: 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) => prompt; the username on HS2 side is whatever is entered in
the prompt
beeline -u (url) => anonymous (no prompt)
!connect (url);user=foo => foo
beeline -u (url);user=foo => anonymous
beeline -n foo -u (url with or without the user) => foo
{noformat}
I'm going to add support for extracting the user from the -u argument, similar
to connect argument
was:
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}
> beeline - support proper usernames based on URL
> -----------------------------------------------
>
> Key: HIVE-18029
> URL: https://issues.apache.org/jira/browse/HIVE-18029
> Project: Hive
> Issue Type: Sub-task
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HIVE-18029.patch
>
>
> Update: 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) => prompt; the username on HS2 side is whatever is entered in
> the prompt
> beeline -u (url) => anonymous (no prompt)
> !connect (url);user=foo => foo
> beeline -u (url);user=foo => anonymous
> beeline -n foo -u (url with or without the user) => foo
> {noformat}
> I'm going to add support for extracting the user from the -u argument,
> similar to connect argument
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
