Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8625A200C10 for ; Fri, 3 Feb 2017 15:21:56 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 84D84160B3F; Fri, 3 Feb 2017 14:21:56 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CF96E160B62 for ; Fri, 3 Feb 2017 15:21:55 +0100 (CET) Received: (qmail 97269 invoked by uid 500); 3 Feb 2017 14:21:55 -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 97258 invoked by uid 99); 3 Feb 2017 14:21:55 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2017 14:21:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id A0449C03A2 for ; Fri, 3 Feb 2017 14:21:54 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id UHFfWMvJqh-a for ; Fri, 3 Feb 2017 14:21:53 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4098C5F30A for ; Fri, 3 Feb 2017 14:21:53 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E2EA9E042C for ; Fri, 3 Feb 2017 14:21:51 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9D3A12528D for ; Fri, 3 Feb 2017 14:21:51 +0000 (UTC) Date: Fri, 3 Feb 2017 14:21:51 +0000 (UTC) From: "Adam Szita (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-14181) DROP TABLE in hive doesn't Throw Error MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 03 Feb 2017 14:21:56 -0000 [ https://issues.apache.org/jira/browse/HIVE-14181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851538#comment-15851538 ] Adam Szita commented on HIVE-14181: ----------------------------------- It is actually the issue in this ticket that if Hive fails to remove data from disk, the Exception is swallowed and success is reported after drop table command execution. (This then leaves data on the disk, but removes the Table from HMS) After my first patch a lot of tests have failed (600+) because of this - a lot of them used to swallow errors that now got to the surface. Nevertheless I added a new Conf key so that this stricter drop_table approach can be switched off/on (default being off). This is now reflected in my 2nd patch ([^HIVE-14181.2.patch]) > DROP TABLE in hive doesn't Throw Error > -------------------------------------- > > Key: HIVE-14181 > URL: https://issues.apache.org/jira/browse/HIVE-14181 > Project: Hive > Issue Type: Bug > Environment: Hive 1.1.0 > CDH 5.5.1-1 > Reporter: Pranjal Singh > Assignee: Adam Szita > Labels: easyfix > Attachments: HIVE-14181.1.patch, HIVE-14181.2.patch > > > drop table table_name doen't throw an error if drop table fails. > I was dropping a table and my trash didn't have enough space to hold the table but the drop table command showed success and the table wasn't deleted. But the hadoop fs -rm -r /hive/xyz.db/table_name/ gave an error "Failed to move to trash" because I didnot have enough space quota in my trash. -- This message was sent by Atlassian JIRA (v6.3.15#6346)