Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1536F9EE1 for ; Wed, 25 Jan 2012 19:54:18 +0000 (UTC) Received: (qmail 55177 invoked by uid 500); 25 Jan 2012 19:54:17 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 55092 invoked by uid 500); 25 Jan 2012 19:54:17 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 55084 invoked by uid 99); 25 Jan 2012 19:54:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jan 2012 19:54:16 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jan 2012 19:54:14 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id A03BF163C71 for ; Wed, 25 Jan 2012 19:53:53 +0000 (UTC) Date: Wed, 25 Jan 2012 19:53:53 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <359201674.77769.1327521233658.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <206691921.61482.1327092882621.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HADOOP-7987) Support setting the run-as user in unsecure mode MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-7987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193258#comment-13193258 ] Hadoop QA commented on HADOOP-7987: ----------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12511871/HADOOP-7987.trunk.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. -1 javadoc. The javadoc tool appears to have generated 7 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/530//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/530//console This message is automatically generated. > Support setting the run-as user in unsecure mode > ------------------------------------------------ > > Key: HADOOP-7987 > URL: https://issues.apache.org/jira/browse/HADOOP-7987 > Project: Hadoop Common > Issue Type: Improvement > Components: security > Affects Versions: 0.23.0, 0.24.0, 1.0.0 > Reporter: Devaraj Das > Assignee: Jitendra Nath Pandey > Fix For: 0.24.0, 0.23.1, 1.1.0 > > Attachments: HADOOP-7987.branch-1.patch, HADOOP-7987.trunk.patch > > > Some applications need to be able to perform actions (such as launch MR jobs) from map or reduce tasks. In earlier unsecure versions of hadoop (20.x), it was possible to do this by setting user.name in the configuration. But in 20.205 and 1.0, when running in unsecure mode, this does not work. (In secure mode, you can do this using the kerberos credentials). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira