[jira] [Updated] (HDFS-13292) Crypto command should give proper exception when trying to set key on existing EZ directory

2018-04-27 Thread Ranith Sardar (JIRA)

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

Ranith Sardar updated HDFS-13292:
-
Description: 
{{Scenario:}}
 # Create a Dir
 # Create EZ for the above dir with Key1
 # Again you can try to create ZONE for same directory with Diff Key i.e Key2

{noformat}
hadoopclient> hadoop key list
Listing keys for KeyProvider: 
org.apache.hadoop.crypto.key.kms.LoadBalancingKMSClientProvider@152aa092
key2
key1
hadoopclient> hdfs dfs -mkdir /kms
hadoopclient> hdfs dfs -put bigdata_env /kms/file1
hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
RemoteException: Attempt to create an encryption zone for a non-empty directory.
hadoopclient> hdfs dfs -rmr /kms/file1
rmr: DEPRECATED: Please use '-rm -r' instead.
Deleted /kms/file1
hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
Added encryption zone /kms
hadoopclient> hdfs crypto -createZone -keyName key2 -path /kms
RemoteException: Attempt to create an encryption zone for a non-empty directory.
hadoopclient>
 {noformat}
Actual Output:
===
 {{Exception should be Like Dir already having the ZONE will not allow to 
create new ZONE on this Dir}}

Expected Output:
=
 {{RemoteException:Attempt to create an encryption zone for non-empty 
directory}}

  was:
{{Scenario:}}
 # Create a Dir
 # Create EZ for the above dir with Key1
 # Again you can try to create ZONE for same directory with Diff Key i.e Key2

{noformat}
hadoopclient> hadoop key list
Listing keys for KeyProvider: 
org.apache.hadoop.crypto.key.kms.LoadBalancingKMSClientProvider@152aa092
key2
key1
hadoopclient> hdfs dfs -mkdir /kms
hadoopclient> hdfs dfs -put bigdata_env /kms/file1
hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
RemoteException: Attempt to create an encryption zone for a non-empty directory.
hadoopclient> hdfs dfs -rmr /kms/file1
rmr: DEPRECATED: Please use '-rm -r' instead.
Deleted /kms/file1
hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
Added encryption zone /kms
hadoopclient> hdfs crypto -createZone -keyName key2 -path /kms
RemoteException: Attempt to create an encryption zone for a non-empty directory.
hadoopclient>
 {noformat}

Actual Output:
===
{{Exception should be Like Dir already having the ZONE will not allow to create 
new ZONE on this Dir}}

Expected Output:
=
{{RemoteException:Attempt to create an encryption zone for non-empty directory}}


> Crypto command should give proper exception when trying to set key on 
> existing EZ directory
> ---
>
> Key: HDFS-13292
> URL: https://issues.apache.org/jira/browse/HDFS-13292
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: hdfs, kms
>Affects Versions: 2.8.3
>Reporter: Harshakiran Reddy
>Assignee: Ranith Sardar
>Priority: Major
> Fix For: 3.2.0
>
> Attachments: HDFS-13292.001.patch, HDFS-13292.002.patch, Screenshot 
> from 2018-04-06 11-48-56.png
>
>
> {{Scenario:}}
>  # Create a Dir
>  # Create EZ for the above dir with Key1
>  # Again you can try to create ZONE for same directory with Diff Key i.e Key2
> {noformat}
> hadoopclient> hadoop key list
> Listing keys for KeyProvider: 
> org.apache.hadoop.crypto.key.kms.LoadBalancingKMSClientProvider@152aa092
> key2
> key1
> hadoopclient> hdfs dfs -mkdir /kms
> hadoopclient> hdfs dfs -put bigdata_env /kms/file1
> hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
> RemoteException: Attempt to create an encryption zone for a non-empty 
> directory.
> hadoopclient> hdfs dfs -rmr /kms/file1
> rmr: DEPRECATED: Please use '-rm -r' instead.
> Deleted /kms/file1
> hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
> Added encryption zone /kms
> hadoopclient> hdfs crypto -createZone -keyName key2 -path /kms
> RemoteException: Attempt to create an encryption zone for a non-empty 
> directory.
> hadoopclient>
>  {noformat}
> Actual Output:
> ===
>  {{Exception should be Like Dir already having the ZONE will not allow to 
> create new ZONE on this Dir}}
> Expected Output:
> =
>  {{RemoteException:Attempt to create an encryption zone for non-empty 
> directory}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[jira] [Updated] (HDFS-13292) Crypto command should give proper exception when trying to set key on existing EZ directory

2018-04-07 Thread Surendra Singh Lilhore (JIRA)

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

Surendra Singh Lilhore updated HDFS-13292:
--
   Resolution: Fixed
Fix Version/s: 3.2.0
   Status: Resolved  (was: Patch Available)

committed to trunk.Thanks!

> Crypto command should give proper exception when trying to set key on 
> existing EZ directory
> ---
>
> Key: HDFS-13292
> URL: https://issues.apache.org/jira/browse/HDFS-13292
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: hdfs, kms
>Affects Versions: 2.8.3
>Reporter: Harshakiran Reddy
>Assignee: Ranith Sardar
>Priority: Major
> Fix For: 3.2.0
>
> Attachments: HDFS-13292.001.patch, HDFS-13292.002.patch, Screenshot 
> from 2018-04-06 11-48-56.png
>
>
> {{Scenario:}}
>  # Create a Dir
>  # Create EZ for the above dir with Key1
>  # Again you can try to create ZONE for same directory with Diff Key i.e Key2
> {noformat}
> hadoopclient> hadoop key list
> Listing keys for KeyProvider: 
> org.apache.hadoop.crypto.key.kms.LoadBalancingKMSClientProvider@152aa092
> key2
> key1
> hadoopclient> hdfs dfs -mkdir /kms
> hadoopclient> hdfs dfs -put bigdata_env /kms/file1
> hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
> RemoteException: Attempt to create an encryption zone for a non-empty 
> directory.
> hadoopclient> hdfs dfs -rmr /kms/file1
> rmr: DEPRECATED: Please use '-rm -r' instead.
> Deleted /kms/file1
> hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
> Added encryption zone /kms
> hadoopclient> hdfs crypto -createZone -keyName key2 -path /kms
> RemoteException: Attempt to create an encryption zone for a non-empty 
> directory.
> hadoopclient>
>  {noformat}
> Actual Output:
> ===
> {{Exception should be Like Dir already having the ZONE will not allow to 
> create new ZONE on this Dir}}
> Expected Output:
> =
> {{RemoteException:Attempt to create an encryption zone for non-empty 
> directory}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[jira] [Updated] (HDFS-13292) Crypto command should give proper exception when trying to set key on existing EZ directory

2018-04-06 Thread Surendra Singh Lilhore (JIRA)

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

Surendra Singh Lilhore updated HDFS-13292:
--
Summary: Crypto command should give proper exception when trying to set key 
on existing EZ directory  (was: Crypto command should give proper exception 
when key is already exist for zone directory)

> Crypto command should give proper exception when trying to set key on 
> existing EZ directory
> ---
>
> Key: HDFS-13292
> URL: https://issues.apache.org/jira/browse/HDFS-13292
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: hdfs, kms
>Affects Versions: 2.8.3
>Reporter: Harshakiran Reddy
>Assignee: Ranith Sardar
>Priority: Major
> Attachments: HDFS-13292.001.patch, HDFS-13292.002.patch, Screenshot 
> from 2018-04-06 11-48-56.png
>
>
> {{Scenario:}}
>  # Create a Dir
>  # Create EZ for the above dir with Key1
>  # Again you can try to create ZONE for same directory with Diff Key i.e Key2
> {noformat}
> hadoopclient> hadoop key list
> Listing keys for KeyProvider: 
> org.apache.hadoop.crypto.key.kms.LoadBalancingKMSClientProvider@152aa092
> key2
> key1
> hadoopclient> hdfs dfs -mkdir /kms
> hadoopclient> hdfs dfs -put bigdata_env /kms/file1
> hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
> RemoteException: Attempt to create an encryption zone for a non-empty 
> directory.
> hadoopclient> hdfs dfs -rmr /kms/file1
> rmr: DEPRECATED: Please use '-rm -r' instead.
> Deleted /kms/file1
> hadoopclient> hdfs crypto -createZone -keyName key1 -path /kms
> Added encryption zone /kms
> hadoopclient> hdfs crypto -createZone -keyName key2 -path /kms
> RemoteException: Attempt to create an encryption zone for a non-empty 
> directory.
> hadoopclient>
>  {noformat}
> Actual Output:
> ===
> {{Exception should be Like Dir already having the ZONE will not allow to 
> create new ZONE on this Dir}}
> Expected Output:
> =
> {{RemoteException:Attempt to create an encryption zone for non-empty 
> directory}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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