This section describes three common methods for upgrading from one MapR Core release to another. The workflows in this
section introduce you to the high-level steps for each method and provide links to pages showing more detail.

After you upgrade MapR core without using the MapR Installer, you need to upgrade ecosystem components with manual steps.
First, verify that your repository is configured to use a MapR Expansion Pack (MEP) that is supported by your cluster
version. Then, upgrade each component manually.

Copy the changes that you made for required services in your existing
hue.ini file into the latest version of the file:

/opt/mapr/hue/hue-<version>/desktop/conf/hue.ini

Note: Hue 3.9 uses the old Query editor to work with Hive and Impala queries,
and introduces new Spark Notebooks. Hue 3.10+ uses Notebooks as a
replacement for the old Query editor for Hive and Impala. If you are
upgrading to Hue 3.10+, and you want to have access to your saved queries in
the old Hive or Impala Query editor, you need to configure Hue to use the
old Query editor. To do this, set the use_new_editor
property in the hue.ini file to false. For
example:

[desktop]
...
# Choose whether to show the new SQL editor.
use_new_editor=false

If you are using MySQL, PostgreSQL, or Oracle, and you have trouble with the
database during the Hue upgrade, you can restore your data from the backup that
you created during the Pre-Upgrade Steps for
Hue: