Return-Path: X-Original-To: apmail-hive-issues-archive@minotaur.apache.org Delivered-To: apmail-hive-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 38F5218FA1 for ; Thu, 12 Nov 2015 20:22:11 +0000 (UTC) Received: (qmail 25343 invoked by uid 500); 12 Nov 2015 20:22:11 -0000 Delivered-To: apmail-hive-issues-archive@hive.apache.org Received: (qmail 25275 invoked by uid 500); 12 Nov 2015 20:22:11 -0000 Mailing-List: contact issues-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list issues@hive.apache.org Received: (qmail 25242 invoked by uid 99); 12 Nov 2015 20:22:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Nov 2015 20:22:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 027B82C1F57 for ; Thu, 12 Nov 2015 20:22:11 +0000 (UTC) Date: Thu, 12 Nov 2015 20:22:11 +0000 (UTC) From: "Szehon Ho (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HIVE-7476) CTAS does not work properly for s3 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/HIVE-7476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Szehon Ho updated HIVE-7476: ---------------------------- Fix Version/s: 1.3.0 Cherry-picked to branch-1 > CTAS does not work properly for s3 > ---------------------------------- > > Key: HIVE-7476 > URL: https://issues.apache.org/jira/browse/HIVE-7476 > Project: Hive > Issue Type: Bug > Affects Versions: 0.13.1, 1.1.0 > Environment: Linux > Reporter: Jian Fang > Assignee: Szehon Ho > Fix For: 1.3.0, 2.0.0 > > Attachments: HIVE-7476.1.patch, HIVE-7476.2.patch, HIVE-7476.3.patch > > > When we use CTAS to create a new table in s3, the table location is not set correctly. As a result, the data from the existing table cannot be inserted into the new created table. > We can use the following example to reproduce this issue. > set hive.metastore.warehouse.dir=OUTPUT_PATH; > drop table s3_dir_test; > drop table s3_1; > drop table s3_2; > create external table s3_dir_test(strct struct) > row format delimited > fields terminated by '\t' > collection items terminated by ' ' > location 'INPUT_PATH'; > create table s3_1(strct struct) > row format delimited > fields terminated by '\t' > collection items terminated by ' '; > insert overwrite table s3_1 select * from s3_dir_test; > select * from s3_1; > create table s3_2 as select * from s3_1; > select * from s3_1; > select * from s3_2; > The data could be as follows. > 1 abc 10.5 > 2 def 11.5 > 3 ajss 90.23232 > 4 djns 89.02002 > 5 random 2.99 > 6 data 3.002 > 7 ne 71.9084 > The root cause is that the SemanticAnalyzer class did not handle s3 location properly for CTAS. > A patch will be provided shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)