sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3018) Hadoop MapReduce job submission be done in client user UGI?
Date Fri, 14 Oct 2016 17:53:20 GMT

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

Jarek Jarcec Cecho commented on SQOOP-3018:
-------------------------------------------

I believe that the right solution here is to use the YARN API that enables us to choose which
queue the job should go to, similarly as HIVE did back in HIVE-8424. That should enable your
use case the same way as impersonating the whole job (which is a security concern)  [~fchn602].

> Hadoop MapReduce job submission be done in client user UGI?
> -----------------------------------------------------------
>
>                 Key: SQOOP-3018
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3018
>             Project: Sqoop
>          Issue Type: New Feature
>          Components: connectors/hdfs
>    Affects Versions: 1.99.7
>            Reporter: Yan Braun
>         Attachments: SQOOP-3018.patch
>
>
> Hdfs Connector read and write to HDFS in client user UGI when proxyUser is enabled. 
But MapReduce job submission is done using Sqoop user UGI, which makes all jobs from different
users run in Sqoop user's hadoop queue  instead of client users' own queue.   
> This is a follow-up JIRA after our discussions with Abraham Fine on whether this will
be on sqoop2 road map in the near future.  Thanks.  



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

Mime
View raw message