sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abraham Fine (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3018) Hadoop MapReduce job submission be done in client user UGI?
Date Thu, 29 Sep 2016 22:59:20 GMT

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

Abraham Fine commented on SQOOP-3018:
-------------------------------------

While our current approach makes sense in some cases (of allowing the connector to pick and
choose which parts of the job are impersonated). I see value in also allowing the entire job
to be impersonated (so jobs are mapped to the correct user). 

I think this should be added as a configuration option for the execution engine. What do you
think [~jarcec]?

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