[SQOOP-891] Sqoop export from S3 to MySQL fails when S3 is not default filesystem.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.1-incubating
• Fix Version/s: 1.4.4
• Component/s: tools

Environment

CDH4.1.3 on Amazon EC2

• Assignee: Unassigned
• Reporter: Jurgen Van Gael
• Created: 12/Feb/13 17:09
• Updated: 20/May/13 16:46
• Resolved: 20/May/13 14:30

Description

I recently tried to use sqoop to export a Hive table that lives on S3 into my MySQL server (sqoop export --options-file config.txt --table _universe --export-dir s3n://key:secret@mybucket/universe --input-fields-terminated-by '\0001' -m 1 --input-null-string '
N' --input-null-non-string '
N'^C). My Sqoop runs on a CDH4 cluster on EC2. I was getting errors such as the following:

13/02/11 17:37:15 ERROR security.UserGroupInformation: PriviledgedActionException as:XXX (auth:SIMPLE) cause:java.io.FileNotFoundException: File does not exist: /universe/000000_0.snappy
13/02/11 17:37:15 ERROR tool.ExportTool: Encountered IOException running export job: java.io.FileNotFoundException: File does not exist: /universe/000000_0.snappy

Since the files do exist on S3, I was reminded of getting the same errors when running Hive queries against this table. The reason Hive was failing back then is because of a bug in CombineFileInputFormat when using it against a non-default file system. These issues have since been fixed in Hadoop:
https://issues.apache.org/jira/browse/MAPREDUCE-1806
https://issues.apache.org/jira/browse/MAPREDUCE-2704
I believe Sqoop uses a version of CombineFileInputFormat but as far as I can tell from the latest sources on GIT hasn't incorporated the above fixes.

Issue Links

• is duplicated by: SQOOP-1033 CombineFileInputFormat does not work with paths not on default FS like ASV