hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Chakka (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HIVE-255) User name is not propagated correctly when a hive server or a web client is issuing hive queries.
Date Wed, 04 Feb 2009 22:59:59 GMT

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

Prasad Chakka updated HIVE-255:
-------------------------------

    Attachment: hive-255.patch

changed user for create table and alter table as well. Not it return error if user information
is not available.

> 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-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.


Mime
View raw message