You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Prasad Chakka (JIRA)" <ji...@apache.org> on 2009/02/04 23:53:59 UTC

[jira] Reopened: (HIVE-255) User name is not propagated correctly when a hive server or a web client is issuing hive queries.

     [ https://issues.apache.org/jira/browse/HIVE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prasad Chakka reopened HIVE-255:
--------------------------------


user name is not getting propagated unless the hadoop.job.ugi information is supplied from hive command line. set hadoop.job.ugi is not having an effect because later calls to getUGI information use cached info instead of new. 

> User name is not propagated correctly when a hive server or a web client is issuing hive queries. 
> --------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-255
>                 URL: https://issues.apache.org/jira/browse/HIVE-255
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Clients
>            Reporter: Prasad Chakka
>            Assignee: Prasad Chakka
>            Priority: Minor
>             Fix For: 0.2.0
>
>         Attachments: hive-255.patch
>
>
> Hive should use the parameter set in hadoop.job.ugi config value instead of user.name which gets overwritten during job submission. Otherwise clients have to set both user.name and hadoop.job.ugi which is clunky.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.