hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HIVE-13085) Need an API / configuration parameter to find out the authenticated user from beeline
Date Thu, 24 Mar 2016 07:13:25 GMT

    [ https://issues.apache.org/jira/browse/HIVE-13085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209893#comment-15209893
] 

Thejas M Nair edited comment on HIVE-13085 at 3/24/16 7:13 AM:
---------------------------------------------------------------

Thanks working on this and contributing to hive [~osayankin] !

I have one concern with this patch, it does not seem like it would work with kerberos mode.
I think the feature ought to work consistently across all authentication modes.

Also note that we already have a 'select username()' feature available via HIVE-9143.



was (Author: thejas):
Would this work in kerberos mode ? (I am not sure if it would).
I think the feature ought to work consistently across all authentication modes.

We already have a 'select username()' feature available via HIVE-9143.


>  Need an API / configuration parameter to find out the authenticated user from beeline
> --------------------------------------------------------------------------------------
>
>                 Key: HIVE-13085
>                 URL: https://issues.apache.org/jira/browse/HIVE-13085
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Oleksiy Sayankin
>            Assignee: Oleksiy Sayankin
>             Fix For: 2.0.0
>
>         Attachments: HIVE-13085.1.patch
>
>
> This request has come from the customer who wanted an API / configuration parameter to
identify the authenticated user from the beeline. This is similar to the request done in the
thread below:
> https://community.hortonworks.com/questions/2620/hadoop-environment-variable-or-configuration-varia.html
> But this would not be a feasible option for the requestor. So here the general ask is
once the user is logged in to the beeline, they wanted to identify who this user is and then
use this information to  enforce the ACLs on the tables through the customer's custom code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message