sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cheolsoo Park (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-543) -hive-import not working with uppercase hostname
Date Wed, 05 Sep 2012 00:19:07 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448239#comment-13448239

Cheolsoo Park commented on SQOOP-543:

Hi Kai,

What sqoop does for hive import is simply invoking the installed hive binaries at the end
of import job. The exception that you're seeing is thrown by hive because it thinks that hostname
must be lower-case, which is along the line with internet standards:
The Internet standards (Request for Comments) for protocols mandate that component hostname
labels may contain only the ASCII letters 'a' through 'z' (in a case-insensitive manner),
the digits '0' through '9', and the hyphen ('-').

We could possibly make sqoop explicitly lowercase hostname before passing it to hive. But
given that the error message which is descriptive as I see it, I think that it is ok as is.
Do you think that lowercasing hostname at Sqoop would be useful?
> -hive-import not working with uppercase hostname
> ------------------------------------------------
>                 Key: SQOOP-543
>                 URL: https://issues.apache.org/jira/browse/SQOOP-543
>             Project: Sqoop
>          Issue Type: Bug
>          Components: hive-integration
>    Affects Versions: 1.3.0
>         Environment: CDH3
>            Reporter: Kai Voigt
> When running the following command, the import fails:
> $ sqoop import --username training --password training --connect jdbc:mysql://Localhost/training
--hive-import --fields-terminated-by '\001' --table Movies
> The error message towards the end reads like this:
> 12/08/08 07:12:32 INFO hive.HiveImport: OK
> 12/08/08 07:12:32 INFO hive.HiveImport: Time taken: 4.098 seconds
> 12/08/08 07:12:32 INFO hive.HiveImport: FAILED: Error in semantic analysis: Line 2:17
Path is not legal 'hdfs://Localhost/user/training/Movies': Move from: hdfs://Localhost/user/training/Movies
to: hdfs://localhost/user/hive/warehouse/movies is not valid. Please check that values for
params "default.fs.name" and "hive.metastore.warehouse.dir" do not conflict.
> 12/08/08 07:12:32 ERROR tool.ImportTool: Encountered IOException running import job:
java.io.IOException: Hive exited with status 10
>         at com.cloudera.sqoop.hive.HiveImport.executeExternalHiveScript(HiveImport.java:349)
>         at com.cloudera.sqoop.hive.HiveImport.executeScript(HiveImport.java:299)
>         at com.cloudera.sqoop.hive.HiveImport.importTable(HiveImport.java:241)
>         at com.cloudera.sqoop.tool.ImportTool.importTable(ImportTool.java:394)
>         at com.cloudera.sqoop.tool.ImportTool.run(ImportTool.java:455)
>         at com.cloudera.sqoop.Sqoop.run(Sqoop.java:146)
>         at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
>         at com.cloudera.sqoop.Sqoop.runSqoop(Sqoop.java:182)
>         at com.cloudera.sqoop.Sqoop.runTool(Sqoop.java:221)
>         at com.cloudera.sqoop.Sqoop.runTool(Sqoop.java:230)
>         at com.cloudera.sqoop.Sqoop.main(Sqoop.java:239)
> Using "localhost" instead of "Localhost" in the command completes the import.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message