RE: Hive in a readonly mode

[Guy Doulberg <Gu...@conduit.com>]

Thanks,

Upgrading hive 0.6 to 0.7 should be a problem?


-----Original Message-----
From: Edward Capriolo [mailto:edlinuxguru@gmail.com] 
Sent: Wednesday, March 30, 2011 4:41 PM
To: user@hive.apache.org
Cc: Guy Doulberg
Subject: Re: Hive in a readonly mode

On Wed, Mar 30, 2011 at 9:29 AM, Guy Doulberg <Gu...@conduit.com> wrote:
> Hey all,
>
> I bet someone has already asked this question before, but I couldn't a
> thread with an answer to it,
>
>
>
> I want to give analysts in my organization access to hive in a readonly way,
>
> I.E, I don't want them to be able to create, drop tables, Alter tables ,
> insert or load.
>
>
>
> How can I do that?
>
>
>
> Thanks, anyway
>
>
>
>
>
>

Hive 0.7.0 has grant/revoke syntax.

If you are looking for a simple solution in a pre "hadoop security"
world: Recursively  own /user/hive/warehouse by a user different then
the user running queries and enable dfs.permissions. This should
prevent anyone from writing to the files. Although jobs running and
failing will be less then optimal. After a few failures hopefully
users will get the point.

Re: Hive in a readonly mode

[Edward Capriolo <ed...@gmail.com>]

On Mon, Apr 4, 2011 at 3:00 AM, Guy Doulberg <Gu...@conduit.com> wrote:
> Thanks,
>
> Upgrading hive 0.6 to 0.7 should be a problem?
>
>
> -----Original Message-----
> From: Edward Capriolo [mailto:edlinuxguru@gmail.com]
> Sent: Wednesday, March 30, 2011 4:41 PM
> To: user@hive.apache.org
> Cc: Guy Doulberg
> Subject: Re: Hive in a readonly mode
>
> On Wed, Mar 30, 2011 at 9:29 AM, Guy Doulberg <Gu...@conduit.com> wrote:
>> Hey all,
>>
>> I bet someone has already asked this question before, but I couldn't a
>> thread with an answer to it,
>>
>>
>>
>> I want to give analysts in my organization access to hive in a readonly way,
>>
>> I.E, I don't want them to be able to create, drop tables, Alter tables ,
>> insert or load.
>>
>>
>>
>> How can I do that?
>>
>>
>>
>> Thanks, anyway
>>
>>
>>
>>
>>
>>
>
> Hive 0.7.0 has grant/revoke syntax.
>
> If you are looking for a simple solution in a pre "hadoop security"
> world: Recursively  own /user/hive/warehouse by a user different then
> the user running queries and enable dfs.permissions. This should
> prevent anyone from writing to the files. Although jobs running and
> failing will be less then optimal. After a few failures hopefully
> users will get the point.
>
As with all upgrades, I suggest testing in a staging environment and
understanding the risks.