[
https://issues.apache.org/jira/browse/HDFS-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495539#comment-13495539
]
Aaron T. Myers commented on HDFS-4148:
--------------------------------------
How about a hybrid solution along the following lines:
* Keep SnapshotException as it is used today, i.e. only for snaphot-related
operations.
* Introduce a new SnapshotAccessControlException which extends
AccessControlException.
* Have this patch throw the new SnapshotAccessControlException wherever a user
tries to modify a RO snapshot.
This way programs which currently handle AccessControlException won't have to
be changed, but programs that do want to differentiate on this basis will be
able to catch a specific exception. This also has the advantage of not
conflating client access errors with snapshot operations exceptions, which I
think are semantically different types of errors.
> 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
