Data Hub Module

Upgrading the Data Hub Module

As part of the upgrade process Spectrum™ Technology Platform backs up the previous Spectrum\server\modules\hub\hub.properties file as well as the Spectrum\server\modules\hub\db\neo4j.properties file. You can use these backups to restore any changes you made to these files; however, it is imperative that you NOT simply copy the new file over the old file because some properties may have been added or removed in the new release.

If you are upgrading Spectrum™ Technology Platform from a version earlier than 12.0, the neo4j.properties file has changed significantly due to the neo4j update from 2.x to 3.x. Please read Spectrum\server\modules\hub\DataHubUpgrade_From_PreV12_README.txt for full details. Also due to this neo4j update, Data Hub upgrades are no longer supported from Spectrum™ Technology Platform 10.x. If you are running 10.0, you must first upgrade to 10.0 SP1, then to 12.0 SP2, and then to 2018.2. If you are running 10.0 SP1, you must first upgrade to 12.0 SP2 and then to 2018.2.

Upgrading Data Hub Indexes

Spectrum™ Technology Platform 2018.2 implements an improved indexing method for better performance. As part of the upgrade to 2018.2, existing indexes will automatically be converted to the new format.

Indexed properties are now restricted to a maximum length of 4039 bytes. If a model has an indexed property that exceeds this limitation, you will not be able to open that model until you complete the following steps.
Note: If you are using the Data Hub Module in a cluster and have hit the maximum index property constraint of 4039 bytes, see "Upgrading a Cluster with the Data Hub Module" in the Spectrum™ Technology Platform Installation Guide.
  1. Stop the Spectrum™ Technology Platform server.
  2. Copy the Spectrum\server\modules\hub\db\neo4j.properties file to the Spectrum\server\modules\hub\db\model.modelName folder for each model that exceeds the property constraint of 4039 characters.
  3. Open the neo4j.properties file(s) that you copied in Step 1. In a text editor, uncomment and set dbms.index.default_schema_provider to lucene+native-1.0. Make sure the neo4j store upgrade is uncommented and that dbms.allow_format_migration is set to true.
  4. Start the Spectrum™ Technology Platform server.
  5. Open all affected Data Hub models.
  6. Remove the Spectrum\server\modules\hub\db\model.modelName\neo4j.properties file(s). By removing this file, version 2.0 of Lucene indexing will now be used by default.
    Note: We recommend that you fix all models that failed upgrade due to the 4039 indexed property constraint and re-index those models to the latest Lucene 2.0 indexes. See the hub model reindex command in the Adminstration Utility section of the Administration Guide.
  7. Stop and restart the Spectrum™ Technology Platform.