{"id":2563,"date":"2018-06-28T00:00:00","date_gmt":"2018-06-28T07:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/autocomplete-in-azure-search-now-in-public-preview"},"modified":"2023-08-02T13:27:11","modified_gmt":"2023-08-02T20:27:11","slug":"autocomplete-in-azure-search-now-in-public-preview","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/autocomplete-in-azure-search-now-in-public-preview\/","title":{"rendered":"Autocomplete in Azure Search now in public preview"},"content":{"rendered":"

Today, we are happy to announce public preview support for autocomplete in Azure Search, one of our most requested features on UserVoice<\/a>. Autocomplete, also called \u201ctype-ahead search\u201d, can enhance the search experience by finding potential terms in the index that match the partial term being written by the user. An example of similar functionality is shown below from bing.com:<\/p>\n

\u00a0\"bing.com\"<\/p>\n

Autocomplete modes<\/h2>\n

For autocomplete to work, the fields in the search index should be listed in a suggester<\/a>. For example, if you define a suggester on a\tcity\tfield, typing “sea” will return terms like \u201cSeattle\u201d or \u201cSeaside\u201d if those terms exist in the city field.<\/p>\n

The table below describes the 3 modes supported by Autocomplete and the expected results in each scenario.<\/p>\n\n\n\n\n\n\n
Mode<\/strong><\/td>\nBehavior<\/strong><\/td>\nQuery<\/strong><\/td>\nAutocompleted results<\/strong><\/td>\n<\/tr>\n
OneTerm<\/td>\nReturns a single term which autocompletes the partial term of the query.<\/td>\n\u201cwhat a wo<\/strong>\u201d<\/td>\n\n

\u201cwomen\u201d<\/p>\n

\u201cwool\u201d<\/p>\n

\u201cworld\u201d<\/p>\n<\/td>\n<\/tr>\n

TwoTerms<\/td>\nReturns a single term and two terms which autocomplete the partial term of the query.<\/td>\n\u201cwhat a wo<\/strong>\u201d<\/td>\n\n

\u201cwonderful day\u201d<\/p>\n

\u201cwolf spider\u201d<\/p>\n

\u201cwoman\u201d<\/p>\n

\u201cworld\u201d<\/p>\n<\/td>\n<\/tr>\n

OneTermWithContext<\/td>\nReturns two terms such that the last two terms from the input query appear together.<\/td>\n\u201cwhat a wonderful d<\/strong>\u201d<\/td>\n\n

\u201cwonderful day\u201d<\/p>\n

\u201cwonderful dog\u201d<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Autocomplete API also supports fuzzy matching in each of these modes. When fuzzy is enabled, it compensates for typos and misspellings, and proposes relevant results based on user intent. For more details about these options, please refer the API documentation<\/a>.<\/p>\n

Suggest vs. Autocomplete<\/h2>\n

For those of you already familiar with Azure Search, you might be wondering how Autocomplete compares to the existing Suggestions feature. Given a partial query term, Suggestions API suggests documents and returns document Ids which contain the query term, while the Autocomplete API returns potential terms from the index which match the partial term in the query. The following examples illustrate the same:<\/p>\n

Suggested results<\/h3>\n

\"Suggest\"<\/a><\/p>\n

Autocompleted results<\/h3>\n

\"Autocomplete\"<\/a><\/p>\n

Next steps<\/h2>\n