Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Message-ID: <1307417.86191291337891435.JavaMail.jira@thor>
Date: Thu, 2 Dec 2010 19:58:11 -0500 (EST)
From: "Paul Butler (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Commented: (HIVE-1763) drop table (or view) should issue
 warning if table doesn't exist
In-Reply-To: <11145746.203611288730192234.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HIVE-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966367#action_12966367 ] 

Paul Butler commented on HIVE-1763:
-----------------------------------

I was concerned about breaking DROP TABLE's idempotence, so rather than throwing an exception I just print the error to the console. If someone can suggest a better approach I'll do it.

> drop table (or view) should issue warning if table doesn't exist
> ----------------------------------------------------------------
>
>                 Key: HIVE-1763
>                 URL: https://issues.apache.org/jira/browse/HIVE-1763
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>            Reporter: dan f
>            Priority: Minor
>         Attachments: HIVE-1763.patch
>
>
> drop table reports "OK" even if the table doesn't exist.  Better to report something like mysql's "Unknown table 'foo'" so that, e.g., unwanted tables (especially ones with names prone to typos) don't persist.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.