Glenn Gilbert

My feedback

  1. 193 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    49 comments  ·  Azure Active Directory » B2C  ·  Flag idea as inappropriate…  ·  Admin →
    Glenn Gilbert supported this idea  · 
  2. 562 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  11 comments  ·  Azure Search » Indexing  ·  Flag idea as inappropriate…  ·  Admin →
    Glenn Gilbert supported this idea  · 
    Glenn 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?

Feedback and Knowledge Base