Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-6891 Follow-on work for transparent data at rest encryption
  3. HDFS-9433

DFS getEZForPath API on a non-existent file should throw FileNotFoundException

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.8.0, 3.0.0-alpha1
    • Component/s: encryption
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Incompatible change, Reviewed
    • Release Note:
      Unify the behavior of dfs.getEZForPath() API when getting a non-existent normal file and non-existent ezone file by throwing FileNotFoundException

      Description

      Presently dfs.getEZForPath() API is behaving differently for a non-existent normal file and non-existent ezone file:

      • If user pass a normal non-existent file then it will return null value. For example, Path("/nonexistentfile")
      • If user pass a non-existent file but which is under an existing encryption zone then it is returning the parent's encryption zone info. For example, Path("/ezone/nonexistentfile")

      Here the proposed idea is to unify the behavior by throwing FileNotFoundException. Please refer the discussion thread.

        Attachments

        1. HDFS-9433-00.patch
          5 kB
          Rakesh R
        2. HDFS-9433-00.patch
          5 kB
          Rakesh R

          Issue Links

            Activity

              People

              • Assignee:
                rakeshr Rakesh R
                Reporter:
                rakeshr Rakesh R
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: