A Suggestions request is a "search-as-you-{type|kind|sort}" {query|question} consisting of a partial string {input|enter} (three character {minimum|minimal}). It returns matching {text|textual content} {found in|present in} suggester-{aware|conscious} fields. Azure Search {looks|appears|appears to be like|seems|seems to be} for matching values in fields {that are|which are|which can be|which might be} predefined in a Suggester. {For example|For instance}, {if you|for those who|if you happen to|in case you|in the event you|should you|when you} {enable|allow} suggestions on a {city|metropolis} {field|area|discipline|subject}, typing "sea" produces {documents|paperwork} containing "Seattle", "Sea Tac", and "Seaside" (all {actual|precise} {city|metropolis} names) for that {field|area|discipline|subject}. {The results|The outcomes} of this operation return {a list|a listing|an inventory} of {suggested|advised|instructed|prompt|recommended|steered|urged} {text|textual content} from matching {documents|paperwork}, plus the {document|doc} key. If matching {text|textual content} is {identical|an identical|equivalent|similar} {across|throughout} {documents|paperwork}, the {suggested|advised|instructed|prompt|recommended|steered|urged} {text|textual content} is repeated. This request is {different|completely different|totally different} than a Search API request. In {application|software|utility} code, you {might|may|would possibly} bind a suggestions {call|name} to keyboard {input|enter}, and a search {call|name} to a search button. A Suggestions operation is issued as a GET or Post request. When {you use|you employ|you utilize} HTTP GET to {call|name} Suggestions, the {length|size} of the request URL {cannot|can not|can't} exceed {8|eight} KB.
This {length|size} is {usually|normally|often} {enough|sufficient} {for most|for many} {applications|functions|purposes}. However, some {applications|functions|purposes} produce very {large|giant|massive} queries, {specifically|particularly} when OData filter expressions are used. For these {applications|functions|purposes}, HTTP Post is {a better|a greater} {choice|alternative|selection} {because|as a result of} it {allows|permits} {larger|bigger} filters than GET. With Post, the {number of|variety of} clauses in a filter is the limiting {factor|issue}, not {the size|the dimensions|the scale} of the {raw|uncooked} filter string {since the|because the|for the reason that} request {size|dimension|measurement} {limit|restrict} for Post is {approximately|roughly} {16|sixteen} MB. {Even though|Although|Despite the fact that|Regardless that|Though} the Post request {size|dimension|measurement} {limit|restrict} {is very|could be very|may be very} {large|giant|massive}, filter expressions {cannot be|can't be} arbitrarily {complex|advanced|complicated}. For {more|extra} {information about|details about} filter complexity limitations, see OData Expression Syntax for Azure Search. HTTPS is required for service requests. The Suggestions request {can be|could be|may be|might be|will be} constructed {using|utilizing} the GET or Post {methods|strategies}. The request URI specifies the {name|identify|title} of the index {to query|to question}. Parameters, such {as the|because the} partially {input|enter} search {term|time period}, are specified on the {query|question} string {in the|within the} case of GET requests, and {in the|within the} request {body|physique} {in the|within the} case of Post requests.
As a {best|finest|greatest} {practice|apply|follow|observe} when creating GET requests, remember to URL-encode {specific|particular} {query|question} parameters when calling {the rest|the remainder|the remaining} API {directly|immediately|instantly|straight}. URL encoding {is only|is barely|is just|is simply} {recommended|advisable|beneficial|really helpful|really useful} on the above {query|question} parameters. {If you|For those who|If you happen to|In case you|In the event you|Should you|When you} inadvertently URL-encode {the entire|all the|the complete|the whole|your complete|your entire} {query|question} string ({everything|all the pieces|all the things|every little thing|every part|every thing|the whole lot} after the ?), requests will break. Also, URL encoding {is only|is barely|is just|is simply} {necessary|crucial|essential|mandatory|needed|obligatory|vital} when calling {the rest|the remainder|the remaining} API {directly|immediately|instantly|straight} {using|utilizing} GET. No URL encoding {is necessary|is critical|is important} when calling Suggestions {using|utilizing} Post, or when {using|utilizing} the Azure Search .Net {client|consumer|shopper} library handles URL encoding for you. Suggestions accepts {several|a number of} parameters that {provide|present} {query|question} {criteria|standards} {and also|and in addition|and likewise} specify search {behavior|conduct|habits}. You {provide|present} these parameters {in the|within the} URL {query|question} string when calling Suggestions {via|by way of|through} GET, and as JSON properties {in the|within the} request {body|physique} when calling Suggestions {via|by way of|through} Post. The syntax for some parameters is {slightly|barely} {different|completely different|totally different} between GET and Post. These {differences|variations} are {noted|famous} in {the following|the next} {table|desk}. {You will also|Additionally, you will} {need|want} the service {name|identify|title} to {construct|assemble} the request URL. {You can get|You may get|You will get} the service {name|identify|title} and api-key {from your|out of your} service dashboard {in the|within the} Azure portal. See Create an Azure Search service {in the|within the} portal for {page|web page} navigation {help|assist}.
Your {old|outdated|previous} Flash {player|participant} {might not|may not|won't} be {compatible|appropriate|suitable} with the {changes|adjustments|modifications}, {which means|which implies|which suggests} {slow|gradual|sluggish} load {times|instances|occasions}, glitches and crashes. {You must|It's essential to|You could|You have to|You need to|You should|You will need to} {download|obtain} {the latest|the most recent|the newest} Flash {player|participant} (Right now it抯 Flash 11) {in order to|as a way to|in an effort to|so as to|to be able to|with a purpose to|with a view to|with the intention to} play new visually-demanding {games|video games} like Hidden Chronicles, Blackwood and Bell Mysteries and future graphic-intensive {games|video games}. {The latest|The most recent|The newest} {version|model} {supports|helps} 3D accelerated rendering, {ensuring|guaranteeing|making certain} uncompromised Flash gaming and {movie|film}-watching {experience|expertise}. {It can be|It may be} {installed|put in} in 64-bit {versions|variations} with ease. Flash {11|eleven} {automatically|mechanically|robotically|routinely} sniffs which OS {version|model} ({64|sixty four} or 32) {you are|you might be|you're} {using|utilizing} {and lets you|and allows you to} {download|obtain} the {version|model} {compatible|appropriate|suitable} {with your|along with your|together with your} OS. Uncheck the McAfee Security scan {if you|for those who|if you happen to|in case you|in the event you|should you|when you} don抰 {want|need} this {feature|characteristic|function}. Once downloaded, {install|set up} the {player|participant} by following the on-{screen|display|display screen} prompts. After {a few|a couple of|a number of|just a few} days, the Flash {player|participant} will ask you for a minor {update|replace}. Follow the steps ({close|shut} Firefox browser {before|earlier than} doing {anything|something}) and {update|replace} the Flash {player|participant}. Now play any {games|video games} on FB and {you will find|one can find|you can find|you can see|you will discover|you will see|you will see that|you'll discover|you'll find} {that most|that almost all|that the majority} {slow|gradual|sluggish} {games|video games} on Facebook will load a bit {quicker|faster}, and {most importantly|most significantly}, won抰 crash when {the game|the sport} {loads|hundreds|masses}.
