hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo Nicholas Sze (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8185) Separate client related routines in HAUtil into a new class
Date Tue, 21 Apr 2015 21:56:59 GMT

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

Tsz Wo Nicholas Sze commented on HDFS-8185:
-------------------------------------------

- Both DFSUtilClient.locatedBlocks2Locations methods are current not used.  Please move them
later.
- DFS_NAMENODE_HTTP_ADDRESS_KEY, DFS_NAMENODE_HTTP_ADDRESS_KEY, etc are namenode confs.
-* In DFSConfigKeys, set DFS_NAMENODE_HTTP_ADDRESS_KEY = HdfsClientConfigKeys.DFS_NAMENODE_HTTP_PORT_DEFAULT
but not deprecate them
-* Namenode, datanode, etc. should keep using the DFSConfigKeys.DFS_NAMENODE_HTTP_ADDRESS_KEY
-* Client will uses HdfsClientConfigKeys.DFS_NAMENODE_HTTP_ADDRESS_KEY.



> Separate client related routines in HAUtil into a new class
> -----------------------------------------------------------
>
>                 Key: HDFS-8185
>                 URL: https://issues.apache.org/jira/browse/HDFS-8185
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: build
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
>         Attachments: HDFS-8185.000.patch, HDFS-8185.001.patch
>
>
> This jira proposes to move the routines used by the client implementation in HAUtil to
a separate class and to move them into the hdfs-client module.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message