[
https://issues.apache.org/jira/browse/HDFS-13045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426027#comment-16426027
]
Íñigo Goiri edited comment on HDFS-13045 at 4/4/18 7:06 PM:
------------------------------------------------------------
Actually, yesterday night I got a little carried away and did a fix for the
exception message: [^HDFS-13045.001.patch].
I went with your first proposal there; I had to remember the original path but
that's fairly simple (didn't check super carefully if there was another place
with the original path though).
was (Author: elgoiri):
Actually, yesterday night I got a little carried away and did a fix for the
exception message.
I went with your first proposal there; I had to remember the original path but
that's fairly simple (didn't check super carefully if there was another place
with the original path though).
> RBF: Improve error message returned from subcluster
> ---------------------------------------------------
>
> Key: HDFS-13045
> URL: https://issues.apache.org/jira/browse/HDFS-13045
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Wei Yan
> Assignee: Wei Yan
> Priority: Minor
> Attachments: HDFS-13045.000.patch, HDFS-13045.001.patch
>
>
> Currently, Router directly returns exception response from subcluster to
> client, which may not have the correct error message, especially when the
> error message containing a path.
> One example, we have a mount path "/a/b" mapped to subclusterA's "/c/d". If
> user1 does a chown operation on "/a/b", and he doesn't have corresponding
> privilege, currently the error msg looks like "Permission denied. user=user1
> is not the owner of inode=/c/d", which may confuse user. Would be better to
> reverse the path back to original mount path.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
