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 D10BD18D2D for ; Fri, 6 Nov 2015 21:52:16 +0000 (UTC) Received: (qmail 28985 invoked by uid 500); 6 Nov 2015 21:52:11 -0000 Delivered-To: apmail-hive-issues-archive@hive.apache.org Received: (qmail 28615 invoked by uid 500); 6 Nov 2015 21:52: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 28506 invoked by uid 99); 6 Nov 2015 21:52:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Nov 2015 21:52:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0F7352C1F63 for ; Fri, 6 Nov 2015 21:52:11 +0000 (UTC) Date: Fri, 6 Nov 2015 21:52:11 +0000 (UTC) From: "Naveen Gangam (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-12184) DESCRIBE of fully qualified table fails when db and table name match and non-default database is in use 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-12184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994522#comment-14994522 ] Naveen Gangam commented on HIVE-12184: -------------------------------------- It was already supported prior to this change. I dint have to do anything specific with my change, except had to be mindful that the tree could contain other children for such usage. There are existing unit tests that tested this behavior clientpositive/describe_xpath.q and clientnegative/describe{1..4}.q > DESCRIBE of fully qualified table fails when db and table name match and non-default database is in use > ------------------------------------------------------------------------------------------------------- > > Key: HIVE-12184 > URL: https://issues.apache.org/jira/browse/HIVE-12184 > Project: Hive > Issue Type: Bug > Components: SQL > Affects Versions: 1.2.1 > Reporter: Lenni Kuff > Assignee: Naveen Gangam > Attachments: HIVE-12184.2.patch, HIVE-12184.3.patch, HIVE-12184.4.patch, HIVE-12184.patch > > > DESCRIBE of fully qualified table fails when db and table name match and non-default database is in use. > Repro: > {code} > : jdbc:hive2://localhost:10000/default> create database foo; > No rows affected (0.116 seconds) > 0: jdbc:hive2://localhost:10000/default> create table foo.foo(i int); > 0: jdbc:hive2://localhost:10000/default> describe foo.foo; > +-----------+------------+----------+--+ > | col_name | data_type | comment | > +-----------+------------+----------+--+ > | i | int | | > +-----------+------------+----------+--+ > 1 row selected (0.049 seconds) > 0: jdbc:hive2://localhost:10000/default> use foo; > 0: jdbc:hive2://localhost:10000/default> describe foo.foo; > Error: Error while processing statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. Error in getting fields from serde.Invalid Field foo (state=08S01,code=1) > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)