We recommend you regularly upgrade LiveData Migrator so you can take advantage of new functionality and other improvements. To upgrade, run a newer version of the LiveData Migrator installer. The installer will upgrade your LiveData Migrator instance to the new version.
If you're running version 1.15.1 or lower, you need to upgrade to LiveData Migrator 1.16.0 before upgrading to any higher versions.
If you want to run the installer using a default user, run the following command:
The default system user for the LiveData Migrator and LiveData UI services is
hdfs, and the default system user for the Hive Migrator service is
If you want to upgrade the product using a custom user and custom group, run the following command:
./livedata-1.17.0-58-full_rpm_installer.sh -- --user <custom user> --group <custom group>
This sets the customer user and group for all services and their respective directories.
For more information, go to Configure system users.
Configuration files stay the same after upgrading, but configuration files from the new version are also added into the same folder on an RPM installation. These new configuration files have the extension
.rpmsave, and are ignored by LiveData Migrator by default. You may compare them and copy changes across accordingly, or use the new files.
The upgrade automatically overwrites shell scripts (such as
start.sh) with the newer versions.
Do not change the value of the encrypted database password value for the UI in
application-prod.properties. If the key changes, the LiveData UI will fail to start. When prompted on an Ubuntu system to keep the old
application-prod.properties file or use the new one from the installer, choose to keep the existing file to prevent this.
Follow the installation instructions to obtain and run a new LiveData Migrator installer. This will upgrade your installed version to the latest.
LiveData Migrator conserves filesystems and migrations during an upgrade. Additionally, migrations in progress prior to the upgrade will continue as normal.
You may check the component versions of your current installation by running
livedata-migrator --version on your LiveData Migrator host machine.
You can continue migrating data as before. Learn how to get started with LiveData Migrator as normal.