Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Sat, 1 Sep 2012 07:30:07 +1100 (NCT)
From: "Robert Joseph Evans (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <566320849.24650.1346445007805.JavaMail.jiratomcat@arcas>
In-Reply-To: <140421455.18313.1346361847505.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (MAPREDUCE-4612) job summary file permissions not
 set when its created
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Joseph Evans updated MAPREDUCE-4612:
-------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.0-alpha
                   3.0.0
                   0.23.3
           Status: Resolved  (was: Patch Available)

Thanks Tom,

I put this into trunk, branch-2, and branch-0.23
                
> job summary file permissions not set when its created
> -----------------------------------------------------
>
>                 Key: MAPREDUCE-4612
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4612
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.23.3, 3.0.0, 2.2.0-alpha
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>            Priority: Critical
>             Fix For: 0.23.3, 3.0.0, 2.2.0-alpha
>
>         Attachments: MAPREDUCE-4612.patch
>
>
> The job summary file permissions are not set when its written out by to the done intermediate directory. The conf and jhist files are both set properly but the summary file doesn't follow the same path.  
> This can cause the summary file to not be copied to the done directory if the default umask is set to be restrictive (like 600) and the mapred user can't read it.

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