[ https://issues.apache.org/jira/browse/SQOOP-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandish Kumar HN resolved SQOOP-3187. ------------------------------------- Resolution: Fixed Fix Version/s: 1.4.7 Upgraded KITE-SDK with the SQOOP-3192 issue. Example Run: sqoop import -D fs.s3n.awsAccessKeyId="" -D fs.s3n.awsSecretAccessKey="" --connect jdbc:mysql://localhost:3306/db1 --username <username> --password <password> --query "select * from t1 where \$CONDITIONS" --num-mappers 1 --target-dir s3n://bucket/dataset/outfolder --as-parquetfile > 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: Sandish Kumar HN > Fix For: 1.4.7 > > > 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.4.14#64029)