Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-13109

Support fully qualified hdfs path in EZ commands

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.1.0, 2.10.0, 2.9.1, 2.8.4, 3.0.3
    • hdfs
    • None
    • Reviewed

    Description

      When creating an Encryption Zone, if the fully qualified path is specified in the path argument, it throws the following error.

      ~$ hdfs crypto -createZone -keyName mykey1 -path hdfs://ns1/zone1
IllegalArgumentException: hdfs://ns1/zone1 is not the root of an encryption zone. Do you mean /zone1?

~$ hdfs crypto -createZone -keyName mykey1 -path "hdfs://namenode:9000/zone2" 
IllegalArgumentException: hdfs://namenode:9000/zone2 is not the root of an encryption zone. Do you mean /zone2?

      The EZ creation succeeds as the path is resolved in DFS#createEncryptionZone(). But while creating the Trash directory, the path is not resolved and it throws the above error.
      A fully qualified path should be supported by crypto.

      Attachments

        1. HDFS-13109.006.patch
          9 kB
          Xiaoyu Yao
        2. HDFS-13109.005.patch
          10 kB
          Hanisha Koneru
        3. HDFS-13109.004.patch
          9 kB
          Hanisha Koneru
        4. HDFS-13109.003.patch
          9 kB
          Hanisha Koneru
        5. HDFS-13109.002.patch
          11 kB
          Hanisha Koneru
        6. HDFS-13109.001.patch
          9 kB
          Hanisha Koneru

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. HDFS-12586 EZ createZone returns IllegalArgumentException when using protocol in path

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              hanishakoneru Hanisha Koneru
              hanishakoneru Hanisha Koneru
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: