#Apache lucene spell check language code#

POST name]./indexes/hotels-sample-index/docs/search?api-version=-Preview With correction, the query returns one result for Johnson's family-oriented resort. Without spell correction, the query returns zero results. The following example uses the built-in hotels-sample index to demonstrate spell correction on a simple free form text query. You can also use beta releases of the Azure SDKs.

#Apache lucene spell check language code#

For REST, you can use Postman, another web client, or code that you've modified to make REST calls to the preview APIs. Use a search client that supports preview APIs on the query request.

Spell check works on strings passed in the 'search' parameter. To use spell check, you'll need the following:Ī search service at Basic tier or above, in any region.Īn existing search index with content in a supported language.Ī query request that has 'speller=lexicon', and 'queryLanguage' set to a supported language. There's no sign-up or extra charges for using this feature. Speller was released in tandem with the semantic search preview and shares the 'queryLanguage' parameter, but is otherwise an independent feature with its own prerequisites.

The speller parameter is supported for all query types: simple, full, and the semantic option currently in public preview. You can improve recall by spell-correcting individual search query terms before they reach the search engine. It's available through the Azure portal and preview REST API only. Spell correction is in public preview under supplemental terms of use.