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

Hadoop QA commented on HADOOP-7603:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12496583/HADOOP-7603-trunk.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified 
tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/233//console

This message is automatically generated.
                
> Set default hdfs, mapred uid, and hadoop group gid for RPM packages
> -------------------------------------------------------------------
>
>                 Key: HADOOP-7603
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7603
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.20.205.0, 0.23.0
>         Environment: Java, Redhat EL, Ubuntu
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>             Fix For: 0.20.205.0, 0.23.0
>
>         Attachments: HADOOP-7603-trunk.patch, HADOOP-7603.patch
>
>
> Hadoop rpm package creates hdfs, mapped users, and hadoop group for 
> automatically setting up pid directory and log directory with proper 
> permission.  The default headless users should have a fixed uid, and gid 
> numbers defined.
> Searched through the standard uid and gid on both Redhat and Debian distro.  
> It looks like:
> {noformat}
> uid: 201 for hdfs
> uid: 202 for mapred
> gid: 49 for hadoop
> {noformat}
> would be free for use.

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

        

Reply via email to