[
https://issues.apache.org/jira/browse/HDFS-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671981#comment-16671981
]
Íñigo Goiri commented on HDFS-13912:
------------------------------------
Making this change, it makes the mount point management similar to a filesystem
(which is fine with me).
I agree that update is there but it is not that flexible.
So the two options are:
* Add this new commands and make it look like a filesystem.
* Make update easier to support the use cases here.
I'm OK with adding the new methods, at some point I may even want to provide a
FileSystem interface for this and be able to do stuff like:
{code}
hdfs dfs -chown user1 mount://mnt1
{code}
Even we could just capture these methods in RouterClientProtocol.
Actually, I'd like to see what happens if I do a chown to a mount point.
Just tested, it does nothing... we could make ClientRouterProtocol smart enough
to manage chown.
Anyway, the question here is the order and readonly ones.
[~dibyendu_hadoop] what is your preference?
> RBF: Add methods to RouterAdmin to set order, read only, and chown
> ------------------------------------------------------------------
>
> Key: HDFS-13912
> URL: https://issues.apache.org/jira/browse/HDFS-13912
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Ayush Saxena
> Assignee: Ayush Saxena
> Priority: Major
> Attachments: HDFS-13912-01.patch, HDFS-13912-02.patch
>
>
> Presently there is methods for only quotas for an existing mount entries.
> Similarly it can be added for the other remaining parameters those even are
> dynamic and requires changes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
