Document version support for data consistency and indexers
External Versioning Support
Are there any plans to support external versioning like the following: https://www.elastic.co/blog/elasticsearch-versioning-support
We are trying to migrate off of an Elasticsearch system where versioning support is being used to allow multiple Indexers potentially processing the same document (potentially different versions of the same document).
By using primary store’s version, we ensure that latest version of document is not overwritten by the older version of document.
I was reading up on stackoverflow (http://stackoverflow.com/questions/28917204/azure-search-data-consistency) even with Etags support, it seems that each writer will need to read the document from AzureSearch to ensure it has the latest version, so will not help in this situation.
Thank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
Azure Search Product Team
Youngjae KIM commented
Like '@search.score' property, it would be good to provide '@search.indextime' as indexed timestamp.
This is useful when we compare documents lifecycle from recorded to utilized moments.
And also, it could be helpful if AzSearch implements time-to-live data as followed by this suggestion; https://feedback.azure.com/forums/263029-azure-search/suggestions/6328648-time-to-live-for-data
When running the index statistics I want to know the last time the index was modified. If I know an entity exists in my data source but I cannot find it in my index, knowing the index is stale would help.