How to manage concurrency in Azure Search
here it is said that Azure Search offers an optimistic concurrency model. There are no locks on a resource. Instead, there is an ETag for every resource that identifies the resource version so that you can craft requests that avoid accidental overwrites.
But Add, Update or Delete Documents (Azure Search Service REST API) has not mentioned anything about etags. Does Azure Search Provides Etags for managing concurrency for Add, Update or Delete Documents?
Unfortunately we do not yet support using document version for managing concurrent add/delete/update operations on documents. As of now, as you mentioned, we only provide etags when managing "non-documents" resources (such as index definitions, synonym maps, data sources, etc.)
Please upvote the following user voice suggestion to help us prioritize the work to add support for document versioning