hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4148) disallow modification on RO snapshots
Date Mon, 12 Nov 2012 19:27:13 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495533#comment-13495533

Suresh Srinivas commented on HDFS-4148:

bq. Agree, though it's a good data point. WAFL/ZFS could have chosen to use EPERM (i.e. operation
not permitted) but they didn't - they chose to use regular old EACCESS. This makes sense because
most client programs don't care much about why they can't access a file, just that they can't.
I prefer having specific exception.

bq. If we separate the two, I suspect what you'll find is that a fair number of user programs
will end up writing identical error handling code for both exceptions, which is a shame.
Most of the client today do not handle specific exception and handle IOException anyway. So
I do not think it should be a real problem.
>  disallow modification on RO snapshots
> --------------------------------------
>                 Key: HDFS-4148
>                 URL: https://issues.apache.org/jira/browse/HDFS-4148
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>    Affects Versions: Snapshot (HDFS-2802)
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>         Attachments: HDFS-4148.patch, HDFS-4148.patch
> disallow modification on RO snapshots, including create, append, setReplication/Permission/Owner,
rename, delete, makedir, setQuota/Time, createSymlink. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message