Upgrading Server¶

As Sqoop server is using external repository for persisting connection and job objects, this repository needs to be updated in addition to updating the server bits. The capability of performing the upgrade has been built-in to the server, however is disabled by default to avoid any unintentional changes to the repository. You can start the upgrade procedure by stopping the server:

./bin/sqoop.sh server stop

It’s strongly advised to back up the repository before moving on to next steps. Precise back-up instructions depends on the repository implementation that is in use, please follow the repository owns instructions to back it up.

Now you can update server bits. Before starting the server again you will need to enable the auto-upgrade feature that will perform all necessary during Sqoop Server boot up procedure. You need to set following properties in configuration file sqoop.properties:

org.apache.sqoop.repository.schema.immutable=false
org.apache.sqoop.connector.autoupgrade=true
org.apache.sqoop.framework.autoupgrade=true

When all properties are set, start server using following command:

./bin/sqoop.sh server start

All required actions will be performed automatically during the server bootstrap procedure. It’s strongly advised to set all three properties to their original values once the server has been successfully started.

Upgrading Client¶

Client do not require any manual steps during upgrade. Replacing the binaries with updated version is sufficient.