IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« 8.0.0 release notes 8.0.0-rc1 release notes »

› ›

8.0.0-rc2 release notes

edit

8.0.0-rc2 release notes

edit

Upgrading to Enterprise Search 8.0.0-rc2? See Upgrading & migrating.

Breaking changes

edit

Changes the index pattern Enterprise Search uses to store monitoring information in Elasticsearch. The new index pattern is .monitoring-ent-search-*.

Bug fixes

edit

Ensures that search boost factors are greater or equal to zero. Using negative boost factors will result in a 400 error response.

Known issues

edit

In rare cases, a Confluence Cloud content source cannot sync. This issue applies only when both of the following are true:
- DLP is enabled for the content source.
- Each Confluence space within the source contains only a few documents.
When restoring data from another deployment’s snapshot in the cloud, Enterprise Search indices are not included in the restore:
- This only occurs when restoring data after a deployment is created.
- Expected behaviour occurs when restoring data from a snapshot during deployment creation.
Workaround:
1. Register the snapshot repository used by cluster 1 on cluster 2.
1. On cluster 1, make a GET _snapshot request, copy the details for the found-snapshots repository.
2. On cluster 2, make the same query, noting the value for "client".
3. On cluster 2, register a new repository using details from cluster 1. This is accomplished with a PUT _snapshot/$NewRepoName request, providing the repo details from step 1a with some modifications. Copy the response body from the above step, but substitute the client value with the client id from step 1b. Additionally, add the setting "readonly": "true" and remove the uuid entry in the json body.
2. Close the enterprise search indices on cluster 2.
3. Restore snapshot from cluster 1 to cluster 2.

« 8.0.0 release notes 8.0.0-rc1 release notes »