Replace your configuration after upgrading. Copy /etc/sqoop/conf from the template to the conf directory in sqoop hosts.

As the HDFS Service user, upload the Apache Sqoop tarball to HDFS.

su -c "hdfs dfs -mkdir -p /hdp/apps/2.2.0.0-<$version>/sqoop" 
                
hdfs su -c "hdfs dfs -chmod -R 555 /hdp/apps/2.2.0.0-<$version>/sqoop" 

hdfs su -c "hdfs dfs -chown -R hdfs:hadoop /hdp/apps/2.2.0.0-<$version>/sqoop" 

hdfs su -c "hdfs dfs -put /usr/hdp/2.2.0.0-<$version>/sqoop/sqoop.tar.gz /hdp/apps/2.2.0.0-<$version>/sqoop/sqoop.tar.gz" 

hdfs su -c "hdfs dfs -chmod 444 /hdp/apps/2.2.0.0-<$version>/sqoop/sqoop.tar.gz"

If you are using the MySQL database as a source or target, then the MySQL connector jar must be updated to 5.1.29 or later.

Refer to the MySQL web site for information on updating the MySQL connector jar.

Because Sqoop is a client tool with no server component, you will need to run your own jobs to validate the upgrade.