Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Sat, 24 Jun 2017 00:24:00 +0000 (UTC)
From: "Gunther Hagleitner (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.13081800.1498141311000.96351.1498263840126@Atlassian.JIRA>
In-Reply-To: <JIRA.13081800.1498141311000@Atlassian.JIRA>
References: <JIRA.13081800.1498141311000@Atlassian.JIRA> <JIRA.13081800.1498141311949@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HIVE-16942) INFORMATION_SCHEMA: schematool for
 setting it up is not idempotent
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 24 Jun 2017 00:24:05 -0000


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

Gunther Hagleitner commented on HIVE-16942:
-------------------------------------------

Patch fixes the problem described, but doesn't make the script idempotent. I'm not sure that's desirable because a non-empty sys db could indicate a problem (existing db). It's fine to drop an empty db though.

[~thejas] review please?

> INFORMATION_SCHEMA: schematool for setting it up is not idempotent
> ------------------------------------------------------------------
>
>                 Key: HIVE-16942
>                 URL: https://issues.apache.org/jira/browse/HIVE-16942
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Carter Shanklin
>            Assignee: Gunther Hagleitner
>         Attachments: HIVE-16942.1.patch
>
>
> If you run schematool to set up information schema, but the SYS database already exists, here's what happens:
> {code}
> [vagrant@trunk apache-hive-3.0.0-SNAPSHOT-bin]$ schematool -metaDbType mysql -dbType hive -initSchema -url jdbc:hive2://localhost:10000/default -driver org.apache.hive.jdbc.HiveDriver
> Metastore connection URL:	 jdbc:hive2://localhost:10000/default
> Metastore Connection Driver :	 org.apache.hive.jdbc.HiveDriver
> Metastore connection User:	 hive
> Starting metastore schema initialization to 3.0.0
> Initialization script hive-schema-3.0.0.hive.sql
> Error: org.apache.hive.service.cli.HiveSQLException: Error while processing statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. Database SYS already exists
> 	at org.apache.hive.service.cli.operation.Operation.toSQLException(Operation.java:315)
> 	at org.apache.hive.service.cli.operation.SQLOperation.runQuery(SQLOperation.java:254)
> {code}
> Why is this a problem you ask?
> If you run schematool without hive.metastore.db.type set (or set to the wrong thing), it will create the sys database but fail to create any of the tables within it. If you go and fix hive.metastore.db.type and re-run you'll get this failure until you drop the SYS database (which must be done as the hive user).
> Can the init script use "create database if not exists sys" rather than just "create database sys"?


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)