[
https://issues.apache.org/jira/browse/HDFS-13326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Íñigo Goiri updated HDFS-13326:
-------------------------------
Description:
>From DFSRouterAdmin cmd, currently the update logic is implemented inside add
>operation, where it has some limitation (e.g. cannot update "readonly" or
>removing a destination). Given the RPC alreadys separate add and update
>operations, it would be better to do the same in cmd level.
was:
1. From DFSRouterAdmin cmd, currently the update logic is implemented inside
add operation, where it has some limitation (e.g. cannot update "readonly" or
removing a destination). Given the RPC alreadys separate add and update
operations, it would be better to do the same in cmd level.
2. Currently in the MountTable tab, the "readonly" field always show empty, no
matter whether the mount entry is readonly or not. From the code perspective,
it tries to show:
{code:java}
<td class="dfshealth-node-icon dfshealth-mount-read-only-{readonly}"/>{code}
The federationhealth.html will load hadoop.css, however the hadoop.css doesn't
have classes with a prefix "dfshealth-mount-read-only". This could be fixed in
HDFS-13204.
> RBF: Improve the interfaces to modify and view mount tables
> -----------------------------------------------------------
>
> Key: HDFS-13326
> URL: https://issues.apache.org/jira/browse/HDFS-13326
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Wei Yan
> Assignee: Gang Li
> Priority: Minor
> Attachments: HDFS-13326.000.patch, HDFS-13326.001.patch
>
>
> From DFSRouterAdmin cmd, currently the update logic is implemented inside add
> operation, where it has some limitation (e.g. cannot update "readonly" or
> removing a destination). Given the RPC alreadys separate add and update
> operations, it would be better to do the same in cmd level.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
