Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

sqoop ERROR tool.ImportTool: Import failed: org.apache.hadoop.fs.UnsupportedFileSystemException: No FileSystem for scheme "null"

avatar
Expert Contributor

Trying to import data from oracle DB and getting error

.... 19/07/31 13:07:10 INFO orm.CompilationManager: Writing jar file: /tmp/sqoop-myuser/compile/375d3de163797c05cd7b480fddcfe58c/QueryResult.jar 19/07/31 13:07:10 ERROR tool.ImportTool: Import failed: org.apache.hadoop.fs.UnsupportedFileSystemException: No FileSystem for scheme "null"     at org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:3281)     at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3301) ....


My sqoop command looks like...

sqoop import \
    -Dmapreduce.map.memory.mb=3144 -Dmapreduce.map.java.opts=-Xmx1048m \
    -Dyarn.app.mapreduce.am.log.level=DEBUG \
    -Dmapreduce.map.log.level=DEBUG \
    -Dmapreduce.reduce.log.level=DEBUG \
    -Dmapred.job.name="Ora import table $tablename" \
    -Djava.security.egd=file:///dev/urandom \
    -Djava.security.egd=file:///dev/urandom \
    -Doraoop.timestamp.string=false \
    -Dmapreduce.map.max.attempts=10 \
    $oracle_cnxn_str \
    --as-parquetfile \
    --target-dir /some/hdfs/path \
    -query "$sqoop_query" \
    --split-by $splitby \
    --where "1=1" \
    --num-mappers 12 \
    --delete-target-dir

Not sure what to make of this error message. Any debugging suggestions or fixes?

1 ACCEPTED SOLUTION

avatar
Expert Contributor

Issue was that the --target-dir path included some variables in the start of the path and ended up with the path looking like

//some/hdfs/path

and the "empty" // was confusing sqoop.

View solution in original post

1 REPLY 1

avatar
Expert Contributor

Issue was that the --target-dir path included some variables in the start of the path and ended up with the path looking like

//some/hdfs/path

and the "empty" // was confusing sqoop.