sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Lin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3187) Sqoop import as PARQUET to S3 failed
Date Sun, 28 May 2017 11:33:04 GMT

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

Eric Lin commented on SQOOP-3187:
---------------------------------

Hi [~sk4sj@yahoo.com],

After checking the source code, I believe that currently Sqoop uses kite-sdk 1.0.0 version,
which does not have s3 support. S3 support only added in kite from version 1.1.0 onwards via
https://issues.cloudera.org/browse/KITE-938.

We will have to wait for kite to be upgraded in Sqoop. I will check further.

> Sqoop import as PARQUET to S3 failed
> ------------------------------------
>
>                 Key: SQOOP-3187
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3187
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.6
>            Reporter: Surendra Nichenametla
>            Assignee: Eric Lin
>
> Sqoop import as parquet file to S3 fails. Command and error are give below.
> However, import to a HDFS location works though.
> sqoop import --connect "jdbc:oracle:thin:@<ip_address>:1521/ORCL" --table mytable
--username myuser --password mypass --target-dir s3://bucket/foo/bar/ --columns col1,col2
-m1 --as-parquetfile
> 17/05/09 21:00:18 ERROR tool.ImportTool: Imported Failed: Wrong FS: s3://bucket/foo/bar,
expected: hdfs://master-ip:8020
> P.S. I tried this from Amazon EMR cluster.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message