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

Pete Wyckoff commented on HADOOP-4106:
--------------------------------------

bq. Does the fuse-dfs currently let me read/write files that I dont have 
permission to do so?

Yes, it does unconditionally. So,  this patch will improve things. the only 
thing is you will get an IO error rather than a correct error message saying 
you don't have permissions. So, in that respect, this patch is an improvement.  
Albeit, getting an IO error rather than a permission error is a little weird. I 
guess the question is whether it's preferable to let people see files 
unconditionally or get an IO error when they do??

I think getting 4108 committed by Friday isn't possible. 

An alternative would be to assume -EPERM when libhdfs gives an error, but that 
would be pretty hacky.






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

Reply via email to