| Table of Contents |
|---|
...
To validate whether any Workbook has been broken during an upgrade, Datameer created the Workbook Health Check feature. The tool reviews a Workbook's structure and reports any logical issues. This tool is available in versions 6.4.14, 7.1.13, 7.2.13, 7.4.11+, 7.5.4+, and 10.0.1+. Datameer's best practice recommendations for upgrades are as follows:
- Upgrade within the current branch to the version where the Workbook Health Check tool is available. For Example, if the current version is 6.4.13, upgrade to 6.4.14.
- Navigate http://<Datameer host>:<port>/dev (admin rights are required), then click on Workbook Health Check and press Start button.
- As soon as validation is complete (execution time varies based on the number and complexity of the existing Workbooks), you will receive a status summary and the broken Workbooks configuration IDs. The same information will also be written into Datameer conductor.log together with the error for every artifact. You might want to review broken Workbooks and fix the errors before the upgrade. Note, a session timeout will interrupt the workbook validation check.
- Upgrade to the desired Datameer version.
- Rerun the Workbook Health Check and ensure that there are no new broken items. In case there are Workbooks that have been broken by the upgrade, check the error messages contained in conductor.log and decide whether you could fix them manually or need to roll back and get Datameer support assistance on the issue.
Backup Keyfiles and Keystore
...
| Note | ||||||
|---|---|---|---|---|---|---|
| ||||||
Example: When upgrading from CDH 4.x to CDH 5.x the classpath was renamed.
to
The correct YARN classpath can be found for the Datameer client via command:
|
Retrigger the Search Index
| Info | ||
|---|---|---|
| ||
The search settings to enable file search within the 'File Browser' must be retriggered manually after the upgrade. |
Recompile Plug-ins
Custom plug-Ins which were created by using the plug-in SDK need to be recompiled. Adjust the versioning and create the plug-in again under the new plug-in SDK.
...