You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Bharathkrishna Guruvayoor Murali (JIRA)" <ji...@apache.org> on 2018/03/30 06:03:00 UTC
[jira] [Commented] (HIVE-16944) schematool -dbType hive should give
some more feedback/assistance
[ https://issues.apache.org/jira/browse/HIVE-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420181#comment-16420181 ]
Bharathkrishna Guruvayoor Murali commented on HIVE-16944:
---------------------------------------------------------
Not able to reproduce the NPE when I give:
{code:java}
$ ./schematool -metaDbType mysql -dbType hive -initSchema
{code}
But schematool does fail because it is not able to interpret the query for initialization properly.
Hence, providing feedback in schematool when the options url/driver are missing when metaDbType is used.
> 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
> Assignee: Bharathkrishna Guruvayoor Murali
> Priority: Major
> Attachments: HIVE-16944.1.patch
>
>
> 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
(v7.6.3#76005)