Solutions to the incompatibility of sqoop versions

This article introduces the relevant knowledge of "the solution to the incompatibility of sqoop version". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Error: incompatible version

Exception in thread "main" java.lang.IncompatibleClassChangeError: Found class org.apache.hadoop.mapreduce.JobContext, but interface was expected at org.apache.sqoop.mapreduce.ExportOutputFormat.checkOutputSpecs (ExportOutputFormat.java:57) at org.apache.hadoop.mapred.JobClient$2.run (JobClient.java:887) at org.apache.hadoop.mapred.JobClient$2.run (JobClient.java:) 850 at java.security.AccessController.doPrivileged (Native Method)....

Solution:

This exception is very typical when someone is messing together incompatible hadoop binaries and applications (for example sqoop compiled for hadoop 2 running on hadoop 1). Would you mind checking that you've downloaded appropriate binary distribution for your cluster? You have to use binary artifact sqoop-1.4.2.bin__hadoop-1.0.0.tar.gz for hadoop 1.0.3.

How to compile it?

Reference: http://my.oschina.net/AlbertHa/blog/318551

This is the end of the content of "sqoop version incompatible Solutions". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!