Goal
This article provides information about the best practices for building Hawksearch Elastic integrations with Sitefinitydocument will provide an insight of the good practices used for working on integrating the Elastic version of the Hawksearch connector.
Setup the Hawksearch engine.
...
The connector creates fields in the Hawksearch engine out of the box. The process of creating the field occurs during the creation of the index. If you want to create additional fields, you can do so from the Administration → Search Indexes (your-website-url/Sitefinity/Administration/search) and you can add additional fields in the Advanced section of the Search Index editor page.
...
Using index mapping provided from the Hawksearch admin page -> Index Mappings (your-website-url/Sitefinity/Administration/indexmappings) more than one developer can use a single index. Developers need to know that if an index is re-indexed, a new index will be created on the engine and all developers who are mapped to this index will not be able to use it due to the difference in the name of the index. In this case, the mapping needs to be updated.
...
Index set as current cannot be deleted. You cannot delete the current index, you can only swap it. You can set current index from Hawksearch admin page -> Hawksearch Indexes (your-website-url/Sitefinity/Administration/hawksearchindexes).
Index set as current cannot be re-indexed. If you try to reindex an index that is set to current, a new index will be created with the same suffix but with a different stamp. If the creation of the new index exceeds the maximum number of indexes (2 for development), the new index will not be created and the reindexing will fail.
Once set the current index cannot be undone. There will always be an index set as current in the respective engine.
...