Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Sqoop Import error (--null-string and --null-non-string)

avatar
Explorer

For a sqoop job with --null-string or --null-non-string the value earlier was <arg></arg>. However it fails with a NullPointerException- Main class [org.apache.oozie.action.hadoop.SqoopMain], exception invoking main(), null.

However changing it to <arg>' '</arg> resolves the issue. In the earlier sqoop version(1.4.6.2.3.4.0-3485) it worked but with the upgraded sqoop version(1.4.6.2.6.0.3-8) it failed with the above error.
1) Is there a fix for this issue on the latest upgraded sqoop version
2) Assuming the work-around that I have mentioned, which is <arg>' '</arg> will the output of the sqoop version remain the same?

1 ACCEPTED SOLUTION

avatar
Rising Star

@Omkar Nalawade As per the Sqoop document,

"The --null-string and --null-non-string arguments are optional.\ If not specified, then the string "null" will be used."

So, in case if you are using --null-string or --null-non-string you will need to pass some value to these arguments. If you want string "null" to be used in place of null values you can ignore these arguments. You can also use '\N' or "\\N" to use null values.

https://community.hortonworks.com/content/supportkb/49673/null-strings-not-handled-by-sqoop-export.h...

View solution in original post

2 REPLIES 2

avatar
Rising Star

@Omkar Nalawade As per the Sqoop document,

"The --null-string and --null-non-string arguments are optional.\ If not specified, then the string "null" will be used."

So, in case if you are using --null-string or --null-non-string you will need to pass some value to these arguments. If you want string "null" to be used in place of null values you can ignore these arguments. You can also use '\N' or "\\N" to use null values.

https://community.hortonworks.com/content/supportkb/49673/null-strings-not-handled-by-sqoop-export.h...

avatar
Explorer

Thanks a lot. Ignoring the --null-string and --null-non-string arguments worked for me.