[ https://issues.apache.org/jira/browse/HDFS-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mingliang Liu updated HDFS-9039: -------------------------------- Attachment: HDFS-9039.000.patch The v0 patch moves code to create NN proxy with _ClientProtocol_ from {{NameNodeProxies}} to {{NameNodeProxiesClient}} class ({{hadoop-hdfs-client}} module). Related classes like {{org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB}} are also moved. With this patch, the {{DFSClient}} class uses {{NameNodeProxiesClient}} class instead of {{NameNodeProxies}}. This will make [HDFS-8053] feasible. > Split o.a.h.hdfs.NameNodeProxies class into two classes in hadoop-hdfs-client > and hadoop-hdfs modules respectively > ------------------------------------------------------------------------------------------------------------------ > > Key: HDFS-9039 > URL: https://issues.apache.org/jira/browse/HDFS-9039 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Mingliang Liu > Assignee: Mingliang Liu > Attachments: HDFS-9039.000.patch > > > Currently the {{org.apache.hadoop.hdfs.NameNodeProxies}} class is used by > both {{org.apache.hadoop.hdfs.server}} package (for server side protocols) > and {{DFSClient}} class (for {{ClientProtocol}}). The {{DFSClient}} class > should be moved to {{hadoop-hdfs-client}} module (see [HDFS-8053 | > https://issues.apache.org/jira/browse/HDFS-8053]). As the > {{org.apache.hadoop.hdfs.NameNodeProxies}} class also depends on server side > protocols (e.g. {{JournalProtocol}} and {{NamenodeProtocol}}), we can't > simply move this class to the {{hadoo-hdfs-client}} module as well. > This jira tracks the effort of moving {{ClientProtocol}} related static > methods in {{org.apache.hadoop.hdfs.NameNodeProxies}} class to > {{hadoo-hdfs-client}} module. A good place to put these static methods is a > new class named {{NameNodeProxiesClient}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)