You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergio Peña (JIRA)" <ji...@apache.org> on 2016/06/16 14:50:05 UTC

[jira] [Commented] (HIVE-13999) Cannot modify mapreduce.job.name at runtime when hive security authorization is enabled

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

Sergio Peña commented on HIVE-13999:
------------------------------------

I don't know how to bypass such issue, but I know that setting {{mapreduce.job.name}} manually can put Hive jobs in restricted Yarn pools.  So, if authorization is enabled, I assume that a check was added to avoid users specify a Yarn pool that they're not allowed to use. Instead, Hive might assign a pool that you're allowed to use based on the HS2 user name.

> Cannot modify mapreduce.job.name at runtime when hive security authorization is enabled 
> ----------------------------------------------------------------------------------------
>
>                 Key: HIVE-13999
>                 URL: https://issues.apache.org/jira/browse/HIVE-13999
>             Project: Hive
>          Issue Type: Bug
>          Components: Authorization, Beeline
>    Affects Versions: 0.14.0
>         Environment: centos 6.5
> ranger 0.4.0
> hive 0.14.0
>            Reporter: gaojun
>              Labels: security
>
> Cannot set mapreduce.job.name at runtime when hive security authorization is enabled !
> I use ranger and enabled hiveserver2 and hivecli security authorization.
> I use hivecli and I can set mapreduce.job.name property by 'set mapreduce.job.name=job1 ' .
> I use beeline and connect the security hiveserver2 , then I run 'set mapreduce.job.name=job1 ' but it is wrong , I get the exception like this :
> Error: Error while processing statement: Cannot modify mapreduce.job.name at runtime. It is not in list of params that are allowed to be modified at runtime (state=42000,code=1).
> so what`s wrong with it?



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