[
https://issues.apache.org/jira/browse/HADOOP-6304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983809#action_12983809
]
Todd Lipcon commented on HADOOP-6304:
-------------------------------------
bq. I also disagree with your aggressive -1-ing without proper discussions and
proposing alternatives within the same context.
Apologies, I certainly didn't mean to come off as aggressive. To me, "-1" means
"this shouldn't be committed as is until changes are made" with the same force
as +1 means "commit away as is". I suppose it has become a loaded term in this
community.
The alternative proposed is HADOOP-7110.
> 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.
