Cloudera Enterprise 5.15.x | Other versions

Upgrading Sqoop 2 from an Earlier CDH 5 Release

Note: Sqoop 2 is being deprecated. Cloudera recommends using Sqoop 1.

These instructions assume that you are upgrading Sqoop 2 as part of an upgrade to the latest CDH 5 release, and have already performed the steps under Upgrading from an Earlier CDH 5 Release to the Latest Release.

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

To upgrade Sqoop 2 from an earlier CDH 5 release, proceed as follows:

Install the new version of Sqoop 2 following directions under Installing Sqoop 2.
If you are running MRv1 on CDH 5 Beta 1 and will continue to run it after upgrading:
1. Update /etc/defaults/sqoop2-server to point to MR1:
```
mv /etc/defaults/sqoop2-server.rpmnew /etc/defaults/sqoop2-server
```
2. Update alternatives:
```
alternatives --set sqoop2-tomcat-conf /etc/sqoop2/tomcat-conf.mr1
```
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.

Page generated May 18, 2018.