This is the documentation for Cloudera 5.5.x. Documentation for other versions is available at Cloudera Documentation.

Upgrading Sqoop 2 from CDH 4 to CDH 5

To upgrade Sqoop 2 from CDH 4 to CDH 5, proceed as follows.


If you have already performed the steps to uninstall CDH 4 and all components, as described under Upgrading from CDH 4 to CDH 5, you can skip Step 1 below and proceed with installing the new CDH 5 version of Sqoop 2.

For more detailed instructions for upgrading Sqoop 2, see the Apache Sqoop Upgrade page.

Step 1: Remove the CDH 4 version of Sqoop 2

To remove Sqoop 2 on a Red Hat-compatible system:

$ sudo yum remove sqoop2-server sqoop2-client

To remove Sqoop 2 on an Ubuntu or other Debian system:

$ sudo apt-get remove sqoop2-server sqoop2-client

To remove Sqoop 2 on a SLES system:

$ sudo zypper remove sqoop2-server sqoop2-client

Step 2: Install the new version of Sqoop 2

  1. Install the new version of Sqoop 2 following directions under Installing Sqoop 2.
  2. If you have been running MRv1 on CDH 4 and will continue to run it on CDH 5:
    1. Update /etc/defaults/sqoop2-server to point to MRv1:
      mv /etc/defaults/sqoop2-server.rpmnew /etc/defaults/sqoop2-server
    2. Update alternatives:
      alternatives --set sqoop2-tomcat-conf /etc/sqoop2/tomcat-conf.mr1
  3. Run the upgrade tool:
    sqoop2-tool upgrade
    This upgrades the repository database to the latest version.
  Important: Configuration files
  • If you install a newer version of a package that is already on the system, configuration files that you have modified will remain intact.
  • If you uninstall a package, the package manager renames any configuration files you have modified from <file> to <file>.rpmsave. If you then re-install the package (probably to install a new version) the package manager creates a new <file> with applicable defaults. You are responsible for applying any changes captured in the original configuration file to the new configuration file. In the case of Ubuntu and Debian upgrades, you will be prompted if you have made changes to a file for which there is a new version; for details, see Automatic handling of configuration files by dpkg.

The upgrade is now complete.

Page generated January 14, 2016.