hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6304) Use java.io.File.set{Readable|Writable|Executable} where possible in RawLocalFileSystem
Date Thu, 20 Jan 2011 00:41:53 GMT

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

Arun C Murthy commented on HADOOP-6304:
---------------------------------------

Todd, this was a stop-gap. Anyway, a foggy day, could you please explain to me the link between
using java.io.File.set{Readable|Writable|Executable} and MAPREDUCE-2238. Thanks.

I agree that HADOOP-7110 will obviate a need for this. But, please be careful with JNI...


> Use java.io.File.set{Readable|Writable|Executable} where possible in RawLocalFileSystem

> ----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6304
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6304
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 0.20.1
>            Reporter: Arun C Murthy
>            Assignee: Arun C Murthy
>         Attachments: HADOOP-6304_yhadoop20.patch
>
>
> Using java.io.File.set{Readable|Writable|Executable} where possible in RawLocalFileSystem
when g & o perms are same saves a lot of 'fork' system-calls.

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


Mime
View raw message