[
https://issues.apache.org/jira/browse/HADOOP-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631543#action_12631543
]
Craig Macdonald commented on HADOOP-4106:
-----------------------------------------
I dont see how this patch can be committed without HADOOP-4104. We know that it
is blocked by it.
Wrt HADOOP-4108, I'm not sure. You need to get (a) a consensus, (b) an
acceptable patch, and (c) the patch committed by Friday.
I think the correction question is whether HADOOP-4108 should be a blocker for
this patch.
Does the fuse-dfs currently let me read/write files that I dont have permission
to do so?
C
> add time, permission and user attribute support to fuse-dfs
> -----------------------------------------------------------
>
> Key: HADOOP-4106
> URL: https://issues.apache.org/jira/browse/HADOOP-4106
> Project: Hadoop Core
> Issue Type: New Feature
> Components: contrib/fuse-dfs
> Reporter: Pete Wyckoff
> Assignee: Pete Wyckoff
> Fix For: 0.19.0
>
> Attachments: HADOOP-4106.txt, HADOOP-4106.txt, HADOOP-4106.txt,
> HADOOP-4106.txt
>
>
> add:
> dfs_chown
> dfs_utime
> dfs_chmod
> Change open to have its own FS on writes (should we do this on reads too??)
> and use it for writes and disconnect when closing the file
> Chane mkdir to open the FS itself and then close it
> also added comments for dfs_access (which needs FileSystem support/libhdfs
> support) and I added the dfs_symlink and truncate since these 3 are the only
> 3 things left as far as functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
