Q: Is it okay for more than one developer to reindex an index at the same time?
A: If more than one developer reindex at the same time, there is a risk that one of the indexes will not be created. Hawksearch currently provides two index slots in the dev environment, and if more than two indexes are created during reindexing, there is a risk that one or more indexes will not be created.
Q: Is it okay for more than one developer to use the same index?
A: Using index mapping provided by the Hawksearch admin page, 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.
Q: Is it okay for more than one developer to create index at the same time?
A: If more than one developer creates an index at the same time, there is a risk that one of the indexes will not be created. Hawksearch currently provides two index slots in the dev environment, and if more than two indexes are created, there is a risk that one or more indexes will not be created.
Q: Is it okay to delete indexes on an engine that more than one developer works?
A: If more than one developer is working on the same engine, deleting of the indexes should be collaborated with others.
Q: Is it okay to create, update or delete items in Sitefinity?
A: When you create, update, or delete items in Sitefinity, updates are automatically reflected in the Hawksearch index. If more than one developer uses the same index, they should be notified for the changes.
Q: Is it okay to set index as a current index?
A: Since there are no direct problems with the existence of the current index, there are things to keep in mind:
...
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-site-domain).
...
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.
...
Working with Hawksearch Lucene
Working with Hawksearch Elastic
Overview
This article provides information about the best practices for building Hawksearch integrations with Sitefinity.