Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-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 6F48619F8E for ; Thu, 14 Apr 2016 01:00:34 +0000 (UTC) Received: (qmail 28525 invoked by uid 500); 14 Apr 2016 01:00:33 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 28334 invoked by uid 500); 14 Apr 2016 01:00:33 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 28068 invoked by uid 99); 14 Apr 2016 01:00:33 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Apr 2016 01:00:33 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 232DC2C1F61 for ; Thu, 14 Apr 2016 01:00:33 +0000 (UTC) Date: Thu, 14 Apr 2016 01:00:33 +0000 (UTC) From: "Mavin Martin (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HADOOP-13023) Distcp with -update feature on first time raw data not working 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/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/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'. 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@769wl02.b13.az2.eng.pdx.wd bin]# hdfs crypto -listZones /tmp/gms/ted DEF0000000000013 [root@769wl02.b13.az2.eng.pdx.wd bin]# hdfs dfs -ls -R /tmp drwxr-xr-x - WD5-SVT.gmspr0022 WD5-SVT.gmspr0022 0 2016-04-14 00:22 /tmp/gms drwxr-xr-x - WD5-SVT.gmspr0022 WD5-SVT.gmspr0022 0 2016-04-14 00:00 /tmp/gms/ted -rw-r--r-- 3 WD5-SVT.gmspr0022 WD5-SVT.gmspr0022 33 2016-04-14 00:00 /tmp/gms/ted/test.txt [root@769wl02.b13.az2.eng.pdx.wd bin]# hadoop distcp -update /.reserved/raw/tmp/gms/ted /.reserved/raw/tmp/gms-with-update/ted [root@769wl02.b13.az2.eng.pdx.wd bin]# hdfs crypto -listZones /tmp/gms/ted DEF0000000000013 [root@769wl02.b13.az2.eng.pdx.wd bin]# hadoop distcp /.reserved/raw/tmp/gms/ted /.reserved/raw/tmp/gms-no-update/ted [root@769wl02.b13.az2.eng.pdx.wd 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/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'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)