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

Amareshwari Sriramadasu commented on HADOOP-4783:
-------------------------------------------------

test-patch result:
     [exec]
     [exec] +1 overall.
     [exec]
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]
     [exec]     +1 tests included.  The patch appears to include 3 new or 
modified tests.
     [exec]
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning 
messages.
     [exec]
     [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
     [exec]
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs 
warnings.
     [exec]
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath 
integrity.
     [exec]
     [exec]     +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
     [exec]

All unit tests passed on my machine

> History files are given world readable permissions.
> ---------------------------------------------------
>
>                 Key: HADOOP-4783
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4783
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0
>            Reporter: Hemanth Yamijala
>            Assignee: Amareshwari Sriramadasu
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: patch-4783-1.txt, patch-4783.txt
>
>
> It is found that history files are being created with permissions 0777. On 
> shared clusters this is opening up too much. However, there is a requirement 
> to allow Chukwa to read history files. (See HADOOP-4705). This issue is to 
> set up appropriate permissions for the files to be as restrictive as 
> required, while still fixing the problem for Chukwa.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to