[
https://issues.apache.org/jira/browse/HDFS-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420182#comment-16420182
]
Gabor Bota commented on HDFS-13363:
-----------------------------------
I'm thinking about two ways to solve this issue:
# Catch AclException in FSDirAclOp, *log* the INode's file path and then throw
the same exception from the catch forward. For this, we need to instantiate a
new logger in FSDirAclOp.
# Create a new AclException, extend message with the path, add the original
exception as cause to preserve call stack, and throw a new exception forward
(wrap it). This would include extending AclException with a suitable
constructor.
> Record file path when FSDirAclOp throws AclException
> ----------------------------------------------------
>
> Key: HDFS-13363
> URL: https://issues.apache.org/jira/browse/HDFS-13363
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Wei-Chiu Chuang
> Assignee: Gabor Bota
> Priority: Minor
>
> When AclTransformation methods throws AclException, it does not record the
> file path that has the exception. Therefore even if it throws an exception,
> we would never know which file has those invalid ACLs.
>
> These AclTransformation methods are invoked in FSDirAclOp methods, which know
> the file path. These FSDirAclOp methods can catch AclException, and then add
> the file path in the error message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
