[jira] [Updated] (HDFS-9433) DFS getEZForPath API on a non-existent file should throw FileNotFoundException

2017-01-19 Thread Junping Du (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Junping Du updated HDFS-9433:
-
Release Note: Unify the behavior of dfs.getEZForPath() API when getting a 
non-existent normal file and non-existent ezone file

> 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
> Fix For: 2.8.0, 3.0.0-alpha1
>
> Attachments: HDFS-9433-00.patch, 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14983301].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

[jira] [Updated] (HDFS-9433) DFS getEZForPath API on a non-existent file should throw FileNotFoundException

2017-01-19 Thread Junping Du (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Junping Du updated HDFS-9433:
-
Release Note: Unify the behavior of dfs.getEZForPath() API when getting a 
non-existent normal file and non-existent ezone file by throwing 
FileNotFoundException  (was: Unify the behavior of dfs.getEZForPath() API when 
getting a non-existent normal file and non-existent ezone file)

> 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
> Fix For: 2.8.0, 3.0.0-alpha1
>
> Attachments: HDFS-9433-00.patch, 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14983301].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

[jira] [Updated] (HDFS-9433) DFS getEZForPath API on a non-existent file should throw FileNotFoundException

2016-09-09 Thread Daryn Sharp (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daryn Sharp updated HDFS-9433:
--
Hadoop Flags: Incompatible change,Reviewed  (was: Reviewed)

> 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
> Fix For: 2.8.0, 3.0.0-alpha1
>
> Attachments: HDFS-9433-00.patch, 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14983301].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

[jira] [Updated] (HDFS-9433) DFS getEZForPath API on a non-existent file should throw FileNotFoundException

2015-11-23 Thread Uma Maheswara Rao G (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Uma Maheswara Rao G updated HDFS-9433:
--
   Resolution: Fixed
 Hadoop Flags: Reviewed
Fix Version/s: 2.8.0
   Status: Resolved  (was: Patch Available)

I have committed this to trunk and branch-2. Thanks Rakesh.

> 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
> Fix For: 2.8.0
>
> Attachments: HDFS-9433-00.patch, 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14983301].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HDFS-9433) DFS getEZForPath API on a non-existent file should throw FileNotFoundException

2015-11-17 Thread Rakesh R (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh R updated HDFS-9433:
---
Attachment: HDFS-9433-00.patch

I'm re-attaching the previous patch again to trigger the build.

> 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, 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14983301].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HDFS-9433) DFS getEZForPath API on a non-existent file should throw FileNotFoundException

2015-11-16 Thread Rakesh R (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh R updated HDFS-9433:
---
Attachment: HDFS-9433-00.patch

> 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14983301].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HDFS-9433) DFS getEZForPath API on a non-existent file should throw FileNotFoundException

2015-11-16 Thread Rakesh R (JIRA) 

 [ 
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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14983301].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HDFS-9433) DFS getEZForPath API on a non-existent file should throw FileNotFoundException

2015-11-16 Thread Rakesh R (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh R updated HDFS-9433:
---
Status: Patch Available  (was: Open)

> 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14983301].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (HDFS-9433) DFS getEZForPath API on a non-existent file should throw FileNotFoundException

2015-11-16 Thread Rakesh R (JIRA) 

 [ 
https://issues.apache.org/jira/browse/HDFS-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh R updated HDFS-9433:
---
Status: Open  (was: Patch Available)

> 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14983301].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)