hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carter Shanklin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16944) schematool -dbType hive should give some more feedback/assistance
Date Thu, 22 Jun 2017 15:44:01 GMT

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

Carter Shanklin commented on HIVE-16944:
----------------------------------------

The dbType hive is specifically for the new INFORMATION_SCHEMA introduced in HIVE-1010

metaDbType only comes into play if you specify dbType of hive.

In this case the metatool is trying to connect to Hive as a JDBC target and create 2 databases
+ a number of tables within them, which is why the HS2 endpoint and driver class are needed.
Although personally I don't see why it can't just hard code org.apache.hive.jdbc.HiveDriver,
but that is a minor point.

> schematool -dbType hive should give some more feedback/assistance
> -----------------------------------------------------------------
>
>                 Key: HIVE-16944
>                 URL: https://issues.apache.org/jira/browse/HIVE-16944
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Carter Shanklin
>
> Given the other ways schematool is used, the most obvious guess I would have for initializing
the Hive schema is:
> {code}
> schematool -metaDbType mysql -dbType hive -initSchema
> {code}
> Unfortunately that fails with this NPE:
> {code}
> Exception in thread "main" java.lang.NullPointerException
> 	at org.apache.hadoop.hive.metastore.tools.HiveSchemaHelper.getDbCommandParser(HiveSchemaHelper.java:570)
> 	at org.apache.hadoop.hive.metastore.tools.HiveSchemaHelper.getDbCommandParser(HiveSchemaHelper.java:564)
> 	at org.apache.hadoop.hive.metastore.tools.HiveSchemaHelper.getDbCommandParser(HiveSchemaHelper.java:560)
> 	at org.apache.hadoop.hive.metastore.tools.HiveSchemaHelper$HiveCommandParser.<init>(HiveSchemaHelper.java:373)
> 	at org.apache.hadoop.hive.metastore.tools.HiveSchemaHelper.getDbCommandParser(HiveSchemaHelper.java:573)
> 	at org.apache.hive.beeline.HiveSchemaTool.getDbCommandParser(HiveSchemaTool.java:165)
> 	at org.apache.hive.beeline.HiveSchemaTool.<init>(HiveSchemaTool.java:101)
> 	at org.apache.hive.beeline.HiveSchemaTool.<init>(HiveSchemaTool.java:90)
> 	at org.apache.hive.beeline.HiveSchemaTool.main(HiveSchemaTool.java:1166)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:498)
> 	at org.apache.hadoop.util.RunJar.run(RunJar.java:233)
> 	at org.apache.hadoop.util.RunJar.main(RunJar.java:148)
> {code}
> Two additional arguments are needed:
> -url jdbc:hive2://localhost:10000/default -driver org.apache.hive.jdbc.HiveDriver
> If the user does not supply these for dbType hive, schematool should detect and error
out appropriately, plus give an example of what it's looking for.



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

Mime
View raw message