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] [Resolved] (SQOOP-665) Submit mapreduce jobs with username retrieved from client
Date Tue, 05 Feb 2013 23:51:14 GMT

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

Jarek Jarcec Cecho resolved SQOOP-665.

    Resolution: Won't Fix

I'm closing this as won't fix as I believe that we do not want to run mapreduce job as the
user who has originated the request. The job will contain sensitive information that the operator
starting the job might not be allowed to see.
> Submit mapreduce jobs with username retrieved from client
> ---------------------------------------------------------
>                 Key: SQOOP-665
>                 URL: https://issues.apache.org/jira/browse/SQOOP-665
>             Project: Sqoop
>          Issue Type: New Feature
>    Affects Versions: 2.0.0
>            Reporter: Jarek Jarcec Cecho
>             Fix For: 2.0.0
> We should execute mapreduce jobs with same username as the one who executed appropriate
command on client side.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message