[
https://issues.apache.org/jira/browse/HADOOP-13023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mavin Martin updated HADOOP-13023:
----------------------------------
Description:
When attempting to do a distcp with the -update feature toggled on encrypted
data, the distcp shows as successful. Reading the encrypted file on the
target_path does not work since the keyName does not exist.
Please see my example to reproduce the issue.
{code}
[root@xxx bin]# hdfs crypto -listZones
/tmp/a/ted DEF0000000000013
[root@xxx bin]# hdfs dfs -ls -R /tmp
drwxr-xr-x - xxx xxx 0 2016-04-14 00:22 /tmp/a
drwxr-xr-x - xxx xxx 0 2016-04-14 00:00 /tmp/a/ted
-rw-r--r-- 3 xxx xxx 33 2016-04-14 00:00 /tmp/a/ted/test.txt
[root@xxx bin]# hadoop distcp -update /.reserved/raw/tmp/a/ted
/.reserved/raw/tmp/a-with-update/ted
[root@xxx bin]# hdfs crypto -listZones
/tmp/a/ted DEF0000000000013
[root@xxx bin]# hadoop distcp /.reserved/raw/tmp/a/ted
/.reserved/raw/tmp/a-no-update/ted
[root@xxx bin]# hdfs crypto -listZones
/tmp/a/ted DEF0000000000013
/tmp/a-no-update/ted DEF0000000000013
{code}
The crypto zone for 'a-with-update' should have been created since this is a
new destination. You can verify this by looking at 'a-no-update'.
was:
When attempting to do a distcp with the -update feature toggled on encrypted
data, the distcp shows as successful. Reading the encrypted file on the
target_path does not work since the keyName does not exist.
Please see my example to reproduce the issue.
{code}
[root@xxx bin]# hdfs crypto -listZones
/tmp/gms/ted DEF0000000000013
[root@xxx bin]# hdfs dfs -ls -R /tmp
drwxr-xr-x - xxx xxx 0 2016-04-14 00:22 /tmp/gms
drwxr-xr-x - xxx xxx 0 2016-04-14 00:00 /tmp/gms/ted
-rw-r--r-- 3 xxx xxx 33 2016-04-14 00:00 /tmp/gms/ted/test.txt
[root@xxx bin]# hadoop distcp -update /.reserved/raw/tmp/gms/ted
/.reserved/raw/tmp/gms-with-update/ted
[root@xxx bin]# hdfs crypto -listZones
/tmp/gms/ted DEF0000000000013
[root@xxx bin]# hadoop distcp /.reserved/raw/tmp/gms/ted
/.reserved/raw/tmp/gms-no-update/ted
[root@xxx bin]# hdfs crypto -listZones
/tmp/gms/ted DEF0000000000013
/tmp/gms-no-update/ted DEF0000000000013
{code}
The crypto zone for 'gms-with-update' should have been created since this is a
new destination. You can verify this by looking at 'gms-no-update'.
> Distcp with -update feature on first time raw data not working
> --------------------------------------------------------------
>
> Key: HADOOP-13023
> URL: https://issues.apache.org/jira/browse/HADOOP-13023
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Mavin Martin
>
> When attempting to do a distcp with the -update feature toggled on encrypted
> data, the distcp shows as successful. Reading the encrypted file on the
> target_path does not work since the keyName does not exist.
> Please see my example to reproduce the issue.
> {code}
> [root@xxx bin]# hdfs crypto -listZones
> /tmp/a/ted DEF0000000000013
> [root@xxx bin]# hdfs dfs -ls -R /tmp
> drwxr-xr-x - xxx xxx 0 2016-04-14 00:22 /tmp/a
> drwxr-xr-x - xxx xxx 0 2016-04-14 00:00 /tmp/a/ted
> -rw-r--r-- 3 xxx xxx 33 2016-04-14 00:00 /tmp/a/ted/test.txt
> [root@xxx bin]# hadoop distcp -update /.reserved/raw/tmp/a/ted
> /.reserved/raw/tmp/a-with-update/ted
> [root@xxx bin]# hdfs crypto -listZones
> /tmp/a/ted DEF0000000000013
> [root@xxx bin]# hadoop distcp /.reserved/raw/tmp/a/ted
> /.reserved/raw/tmp/a-no-update/ted
> [root@xxx bin]# hdfs crypto -listZones
> /tmp/a/ted DEF0000000000013
> /tmp/a-no-update/ted DEF0000000000013
> {code}
> The crypto zone for 'a-with-update' should have been created since this is a
> new destination. You can verify this by looking at 'a-no-update'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
