We plan to start work on this in the next 6 months. Please note we don’t have timing on when it would be available for customers.
562 votesGlenn Gilbert commented
We are going to be running a web job periodically to replace an entire dataset on a search index. I'm working to figure out how to replace the entire dataset within Azure Search, without affecting any active traffic.
I've used Elasticsearch before and it's concept of Index Alias' (https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-aliases.html) achieves this.
The idea is that the alias is a URL front door for the search and internally directs to a specified index. When replacing the data set, the builder creates a new index (typically with a datetime stamp in the index name), populates and verifies the index. If that succeeds, the alias is then switched to the new index and all traffic atomically redirects to the new index, leaving the old index to be deleted.
Does Azure Search have a concept or mechanism that allows the same atomic behaviour or replacing an index?
Is it as simple as exposing the alias functionality with Azure Search as the facade?