For Autocomplete, URL-encoding might be necessary for the following query parameters: Remember to URL-encode specific query parameters when calling the GET REST API directly. For queries, the api-version is always specified as a URI parameter for both GET and POST. The current stable version is api-version=. Specifies the documents collection of a named index. Set this to the unique, user-defined name of your search service. For more information about filter complexity limitations, see OData Expression Syntax for Azure Cognitive Search. Even though the POST request size limit is very large, filter expressions cannot be arbitrarily complex. With POST, the number of clauses in a filter is the limiting factor, not the size of the raw filter string since the request size limit for POST is approximately 16 MB.
For these applications, HTTP POST is a better choice because it allows larger filters than GET. However, some applications produce very large queries, specifically when OData filter expressions are used. This length is usually enough for most applications. When called with GET, the length of the request URL cannot exceed 8 KB. POST name]./indexes//docs/autocomplete?api-version= The Autocomplete request can be constructed using the GET or POST methods. Internally, the search engine looks for matching terms in fields that have a Suggester configured. For example, if the query input is "medic", the Autocomplete API will return "medicare", "medicaid", "medicine" if those terms are in the index. The Autocomplete API finishes a partially typed query input using existing terms in the search index for use in a secondary query.
0 kommentar(er)
