Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 26 Oct 2011 04:57:32 +0000 (UTC)
From: "Ashutosh Chauhan (Commented) (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: 
 <300533990.16653.1319605052199.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <735126768.7409.1318963631399.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HIVE-2510) Hive throws Null Pointer Exception
 upon CREATE TABLE <db_name>.<table_name> ....     if the given <db_name>
 doesn't exist
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HIVE-2510?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13135=
708#comment-13135708 ]=20

Ashutosh Chauhan commented on HIVE-2510:
----------------------------------------

It would be better to check for table existence and db existence together i=
n CTAS within analyzeCreateTable(). Its little awkward that we check for ta=
ble existence first and db existence later. But, I don't you want you to fo=
rce into doing another patch. Will leave it upto committers. Otherwise, loo=
ks good to me.=20
               =20
> Hive throws Null Pointer Exception upon CREATE TABLE <db_name>.<table_nam=
e> ....     if the given <db_name> doesn't exist
> -------------------------------------------------------------------------=
------------------------------------------------
>
>                 Key: HIVE-2510
>                 URL: https://issues.apache.org/jira/browse/HIVE-2510
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Robert Sur=C3=B3wka
>            Assignee: Robert Sur=C3=B3wka
>            Priority: Trivial
>         Attachments: HIVE-2510.1.patch, HIVE-2510.2.patch, HIVE-2510.3.pa=
tch, HIVE-2510.4.patch, HIVE-2510.5.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira