hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-9022) Move NameNode.getAddress() and NameNode.getUri() to hadoop-hdfs-client
Date Thu, 17 Sep 2015 21:19:04 GMT

     [ https://issues.apache.org/jira/browse/HDFS-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Haohui Mai updated HDFS-9022:
    Component/s:     (was: namenode)

> Move NameNode.getAddress() and NameNode.getUri() to hadoop-hdfs-client
> ----------------------------------------------------------------------
>                 Key: HDFS-9022
>                 URL: https://issues.apache.org/jira/browse/HDFS-9022
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>            Reporter: Mingliang Liu
>            Assignee: Mingliang Liu
>             Fix For: 2.8.0
>         Attachments: HDFS-9022.000.patch, HDFS-9022.001.patch, HDFS-9022.002.patch, HDFS-9022.003.patch,
> The static helper methods in NameNodes are used in {{hdfs-client}} module. For example,
it's used by the {{DFSClient}} and {{NameNodeProxies}} classes which are being moved to {{hadoop-hdfs-client}}
module. Meanwhile, we should keep the {{NameNode}} class itself in the {{hadoop-hdfs}} module.
> This jira tracks the effort of moving the following static helper methods out of  {{NameNode}}
and thus {{hadoop-hdfs}} module. A good place to put these methods is the {{DFSUtilClient}}
> {code}
> public static InetSocketAddress getAddress(String address);
> public static InetSocketAddress getAddress(Configuration conf);
> public static InetSocketAddress getAddress(URI filesystemURI);
> public static URI getUri(InetSocketAddress namenode);
> {code}
> Be cautious not to bring new checkstyle warnings.

This message was sent by Atlassian JIRA

View raw message