[
https://issues.apache.org/jira/browse/HDFS-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694293#comment-16694293
]
Ayush Saxena edited comment on HDFS-14085 at 11/21/18 11:51 AM:
----------------------------------------------------------------
[~elgoiri] [~ajisakaa] Thanks for the agreement!!!
By far as solution is concerned.
I would prefer it to be an on call operation to get those details only when the
command is called rather than having any overhead running always.Since this ls
on mount points doesn't seems to be a frequent operation.Whenever it is called
we can get the correct info at that time only.
As far as implementation is concerned we can get the correct details from the
getFileInfoAll(..) API with destination of mount point passed as parameter
that is already there and as of now we can use the same behavior it has for
multiple destination.
Just a minor thought.While adding multiple destinations we could have verified
that all destinations have same permissions and owner details and then all ADD
rather than getting into such a situation.But this would be a problem if the
dest is not already present :(
[~surendrasingh] Any suggestions?
was (Author: ayushtkn):
[~elgoiri] [~ajisakaa] Thanks for the agreement!!!
By far as solution is concerned.
I would prefer it to be an on call operation to get those details only when the
command is called rather than having any overhead running always.Since this ls
on mount points doesn't seems to be a frequent operation.Whenever it is called
we can get the correct info at that time only.
As far as implementation is concerned we can get the correct details from the
getFileInfo(..) API that is already there and as of now we can use the same
behavior it has for multiple destination.
IMO If we want to improve further the getFileInfo(..) we can track that too
separately,
Just a minor suggestion.While adding multiple destinations we could have
verified that all destinations have same permissions and owner details and then
all ADD rather than getting into such a situation.
[~surendrasingh] Any suggestions?
> RBF: LS command for root shows wrong owner and permission information.
> ----------------------------------------------------------------------
>
> Key: HDFS-14085
> URL: https://issues.apache.org/jira/browse/HDFS-14085
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Ayush Saxena
> Assignee: Ayush Saxena
> Priority: Major
>
> The LS command for / lists all the mount entries but the permission displayed
> is the default permission (777) and the owner and group info same as that of
> the user calling it; Which actually should be the same as that of the
> destination of the mount point.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
