Version 0.7.0

Version 0.7.0 depends on Hops This Hops version requires a change of the type of the Inode ID. This requires modifications to the cluster definition and some manual intervention.

Changes to the cluster definition

  1. In the global attrs section add the current version attribute. The attribute should be set to your current installed version. Example:
        current_version: "0.6.1"
  1. The upgrade requires rebuilding the Elasticsearch index for projects and datasets. Force the rebuilding by adding the following attribute to the cluster definition:
        reindex: "true"
  1. If your installation includes Hive, and you are installing it using the hive2::default or hive2 entries in your recipes list, you should replace it with:
    - hive2::db
    - hive2::tez
    - hive2::server2
    - hive2::metastore
  1. In version 0.7.0 we have promoted conda to a first-level Chef cookbook. For every nodes group in the groups section, add the following block in the recipes section. Order does not matter.
- conda

Manual actions required

The Inode ID type change requires several modifications of the database schema. Before starting the upgrade, make sure you have a backup of your database. Before starting the upgrade you should disable the foreign key checks in MySQL.

set global FOREIGN_KEY_CHECKS=0;

Once the hive2::db recipe has run successfully you can proceed to re-enable the foreign key checks.

set global FOREIGN_KEY_CHECKS=1;

As a heads up, the setting is restored to 1 if you restart your MySQL server.