[jira] [Commented] (HIVE-18029) beeline - support proper usernames based on the URL arg
[
https://issues.apache.org/jira/browse/HIVE-18029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279781#comment-16279781
]
Lefty Leverenz commented on HIVE-18029:
---
Okay, thanks Sergey.
> beeline - support proper usernames based on the URL arg
> ---
>
> Key: HIVE-18029
> URL: https://issues.apache.org/jira/browse/HIVE-18029
> Project: Hive
> Issue Type: Sub-task
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 3.0.0
>
> 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)
[jira] [Commented] (HIVE-18029) beeline - support proper usernames based on the URL arg
[
https://issues.apache.org/jira/browse/HIVE-18029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279242#comment-16279242
]
Sergey Shelukhin commented on HIVE-18029:
-
Probably not, it's more of a bugfix.
> beeline - support proper usernames based on the URL arg
> ---
>
> Key: HIVE-18029
> URL: https://issues.apache.org/jira/browse/HIVE-18029
> Project: Hive
> Issue Type: Sub-task
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 3.0.0
>
> 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)
[jira] [Commented] (HIVE-18029) beeline - support proper usernames based on the URL arg
[
https://issues.apache.org/jira/browse/HIVE-18029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278300#comment-16278300
]
Lefty Leverenz commented on HIVE-18029:
---
Does this need to be documented in the wiki?
* [Beeline Command Options |
https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients#HiveServer2Clients-BeelineCommandOptions]
> beeline - support proper usernames based on the URL arg
> ---
>
> Key: HIVE-18029
> URL: https://issues.apache.org/jira/browse/HIVE-18029
> Project: Hive
> Issue Type: Sub-task
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 3.0.0
>
> 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)
