Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 104D218C1F for ; Mon, 16 Nov 2015 18:56:12 +0000 (UTC) Received: (qmail 15721 invoked by uid 500); 16 Nov 2015 18:56:11 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 15530 invoked by uid 500); 16 Nov 2015 18:56:11 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 15496 invoked by uid 99); 16 Nov 2015 18:56:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Nov 2015 18:56:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 028192C1F5E for ; Mon, 16 Nov 2015 18:56:11 +0000 (UTC) Date: Mon, 16 Nov 2015 18:56:11 +0000 (UTC) From: "Rakesh R (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-9433) DFS getEZForPath API on a non-existent file should throw FileNotFoundException MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated HDFS-9433: --------------------------- Target Version/s: 2.8.0 Status: Patch Available (was: Open) Attaching patch to throw FNFException on non-existent file. Please review the changes, thanks! > DFS getEZForPath API on a non-existent file should throw FileNotFoundException > ------------------------------------------------------------------------------ > > Key: HDFS-9433 > URL: https://issues.apache.org/jira/browse/HDFS-9433 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: encryption > Reporter: Rakesh R > Assignee: Rakesh R > Attachments: HDFS-9433-00.patch > > > 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|https://issues.apache.org/jira/browse/HDFS-9348?focusedCommentId=14983301&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14983301]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)