Skip to main content

Elasticsearch - Migration Procedure Version 7.0 to 7.1 (and 6.1 to 6.2)

Abstract

Elasticsearch - Migration Procedure Version 7.0 to 7.1 (and 6.1 to 6.2)

The index of Elasticsearch has changed. When migrating PoolParty instances from version 7.0 to 7.1 and 6.1 to 6.2, you have to use the following procedure.

Corpusterm Index Update:

  • <PPAppDir>/poolparty/data/elasticsearch/corpusterm

Also delete the respective index in this folder: ${elasticsearch.home}/data

Conceptdata Index Update:

On Elasticsearch delete this folder:

  • <PPAppDir>/data/elasticsearch/conceptdata

Also delete the respective index in this folder: ${elasticsearch.home}/data

Elasticsearch API Call for Folder Deletion:

Elasticsearch has published an API call for deleting these folders, in the PoolParty compliant version find details on their website.

Index Migration for GraphSearch with PoolParty Semantic Integrator and Elasticsearch:

The GraphSearch Elasticsearch searchdata index changed. Follow this procedure for migrating it.

Export and Delete the Index:

  1. Open the GraphSearch Admin Dashboard and export the indices of all Search Spaces.

  2. Stop the GraphSearch and Elasticsearch servers and delete the searchdata index.

  3. Start Elasticsearch and GraphSearch. This will re-create the searchdata core.

  4. Import the indices you exported before, using the GraphSearch Admin Dashboard.

Change the Index Manually:

  1. Stop the GraphSearch and Elasticsearch server.

  2. Change the index as follows for Elasticsearch:

    • Download the settings.json file.

    • Replace the existing file in this folder with the new one: <PPAppDir>data/elasticsearch/searchdata

  3. Start Elasticsearch and GraphSearch.

  4. Migrate data using the API call: /GraphSearch/admin/migrate

In this section: