Upgrading external Elasticsearch clusters to Elasticsearch 7
V20.0.0.2 From Process Federation Server V20.0.0.2 onwards, using an external Elasticsearch 6.x cluster is no longer supported. Instead, you must set up an external Elasticsearch 7.x (from 7.8.0) cluster (see Elasticsearch product end of life dates at https://www.elastic.co/support/eol).
The migration to Elasticsearch 7 clusters brings in two major changes:
- There no longer is a document type for the documents stored by Process Federation Server in Elasticsearch indices (as a result of the mapping types removal in Elasticsearch 7: https://www.elastic.co/guide/en/elasticsearch/reference/current/removal-of-types.html)
- As index names starting with "." are deprecated in Elasticsearch 7 (see https://www.elastic.co/guide/en/elasticsearch/reference/7.x/indices-create-index.html), when a federated system is declared with an index name of myIndexName, the created index has the name @myIndexName. In Elasticsearch 6, an index named .myIndexName was created with an alias of myIndexName.
If you migrate to Process Federation Server V21.0.3 from an existing topology based on an Elasticsearch 6.x cluster for indexing, you must either rebuild your federated systems indexes from scratch, or migrate your existing Elasticsearch 6.x indices to Elasticsearch 7.x.