[ 
https://issues.apache.org/jira/browse/HDFS-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16670175#comment-16670175
 ] 

Ayush Saxena commented on HDFS-13912:
-------------------------------------

[~elgoiri] if this works
{code:java}
hdfs dfsrouteadmin -update /mnt -readonly
{code}
Then it could be an alt.But Looking at the code it actually doesn't seems to 
me.Destination is a mandatory field for update.
 Nevertheless we won't reach that logic only.The min argument check only will 
throw us out before only. :P
 And Moreover if we try to outsmart this existing logic.We will land up in 
something similar situation as HDFS-13835 and develop a completely wrong 
perspective about the functionality. 
 HDFS-13853 by description what is given is nowhere in the picture for me.It 
deals with coding part to remove replacement of values to updating the value(I 
guess preventing discard of existing values). Nothing more is mentioned 
anywhere .This remains as it was before and after.And no where is effected or 
effects.
 Moreover, Whichever way we go.By now IIUC these operations are simply not 
possible according to me and the present update is more like update the 
structure which allows us to modify these values as an add-on as a thought that 
when structure is getting modified these addl. paramas might also get changed 
and this sounds quite genuine to me.
 There is nothing to my belief that handles this. Correct me If wrong.
 IMO I would prefer that the commands which would be so readily used when in 
practical environments should be little user friendly and understandable too as 
I don't expect the user to be too friendly with the internal code logics.
 A simple operation should be simple only as HDFS-13835 wanted to change order 
landed up doing something vague(Won't add what went wrong there logically).
 Over to you :)

> 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]

Reply via email to