Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-6200 Create a separate jar for hdfs-client
  3. HDFS-9039

Separate client and server side methods of o.a.h.hdfs.NameNodeProxies

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.8.0, 3.0.0-alpha1
    • None
    • None
    • Reviewed

    Description

      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 ). 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.

      The checkstyle warnings can be addressed in HDFS-8979, and removing the slf4j logger guards when calling LOG.debug() and LOG.trace() can be addressed in HDFS-8971.

      Attachments

        1. HDFS-9039.000.patch
          216 kB
          Mingliang Liu
        2. HDFS-9039.001.patch
          42 kB
          Mingliang Liu
        3. HDFS-9039.002.patch
          44 kB
          Mingliang Liu

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            liuml07 Mingliang Liu
            liuml07 Mingliang Liu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment