Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 25 Oct 2011 17:42:32 +0000 (UTC)
From: =?utf-8?Q?Robert_Sur=C3=B3wka_=28Updated=29_=28JIRA=29?=
 <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: 
 <2082568281.14397.1319564552279.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <198086158.5830.1318442473051.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HIVE-2501) When new instance of Hive (class) is
 created, the current database is reset to default (current database
 shouldn't be changed).
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/HIVE-2501?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Sur=C3=B3wka updated HIVE-2501:
---------------------------------

    Attachment: HIVE-2501.2.patch

Thank you for the response.

The current diff at: https://reviews.apache.org/r/2361/diff/#index_header

I added the appropriate test.

About the previous .q test, I believe that new database wouldn't be created=
 for each .q file, unless also tables like src and src_part are recreated f=
or each .q file - but now it is immaterial anyway.  =20
               =20
> When new instance of Hive (class) is created, the current database is res=
et to default (current database shouldn't be changed).
> -------------------------------------------------------------------------=
------------------------------------------------------
>
>                 Key: HIVE-2501
>                 URL: https://issues.apache.org/jira/browse/HIVE-2501
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Robert Sur=C3=B3wka
>            Assignee: Robert Sur=C3=B3wka
>            Priority: Minor
>         Attachments: HIVE-2501.1.patch, HIVE-2501.2.patch
>
>
> This bug manifested to me, when first thing I did after starting Hive, wa=
s to call use <db_name>; but then calling show tables; was still showing ta=
bles from the default database (and I had to call "use" again to actually c=
hange database). This bug might have manifested only due to a specific Hive=
 deployment I am using (I didn't investigate this issue that deeply).=20

--
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