sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Afsal Thaj (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-475) Unable to import into external hive table located on S3
Date Wed, 27 Jun 2012 09:51:44 GMT

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

Afsal Thaj commented on SQOOP-475:
----------------------------------

Got the same error while trying to move from mysql to hdfs to hive
                
> Unable to import into external hive table located on S3
> -------------------------------------------------------
>
>                 Key: SQOOP-475
>                 URL: https://issues.apache.org/jira/browse/SQOOP-475
>             Project: Sqoop
>          Issue Type: Bug
>          Components: hive-integration
>    Affects Versions: 1.4.1-incubating
>         Environment: Amazon EMR
> Hadoop 0.20.205
> Hive 0.7.1
> Sqoop 1.4.1-incubating
>            Reporter: Porati S├ębastien
>
> When i try to import into an hive table located on an S3 bucket, i got the following
error message :
> FAILED: Error in semantic analysis: Line 2:17 Path is not legal 'hdfs://10.48.189.XX:9000/user/hadoop/client':
Move from: hdfs://10.48.189.XX:9000/user/hadoop/client to: s3://some-bucket/sqoop-test/hive/client
is not valid. Please check that values for params "default.fs.name" and "hive.metastore.warehouse.dir"
do not conflict.
> Hive table creation Script :
> CREATE DATABASE IF NOT EXISTS sqoop_test;
> USE sqoop_test;
> CREATE EXTERNAL TABLE IF NOT EXISTS client (
>     id INT,
>     email STRING,
>     cookie_uid STRING,
>     is_blacklisted TINYINT
> )
> LOCATION 's3://some-bucket/sqoop-test/hive/client';
> Sqoop command :
> sqoop import --connect jdbc:mysql://my.domain.com/mydb --username myuser --password XXXX
--table client --hive-import --hive-overwrite --hive-table sqoop_test.client

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message