Sunday, 29 September 2019

As You Add And Delete Documents




This {section|part} describes {how to|easy methods to|find out how to|how one can|how you can|learn how to|methods to|the best way to|the right way to|the way to|tips on how to} configure suggesters so {you can|you may|you possibly can|you'll be able to} retrieve suggestions. Suggestions are {possible|attainable|doable|potential} matches for an incomplete search query梩hey {enable|allow} you to {display|show} {likely|doubtless|possible|probably|seemingly} matches {before|earlier than} {users|customers} {finish|end} typing their queries. In Amazon CloudSearch, suggestions are {based|based mostly|primarily based} on the contents of {a particular|a selected|a specific} {text|textual content} {field|area|discipline|subject}. {When you|If you|Once you|Whenever you|While you} request suggestions, Amazon CloudSearch finds {all of the|all the|the entire} {documents|paperwork} whose values {in the|within the} suggester {field|area|discipline|subject} {start|begin} with {the specified|the desired|the required} {query|question} string梩he {beginning|starting} of {the field|the sector|the sphere} {must|should} match the {query|question} string to be {considered|thought of|thought-about} a match. The return {data|information|knowledge} {includes|consists of|contains} {the field|the sector|the sphere} {value|worth} and {document|doc} ID for {each|every} match. {You can|You may|You possibly can|You'll be able to} configure suggesters {to find|to search out|to seek out} matches for {the exact|the precise} {query|question} string, or to {perform|carry out} approximate string matching (fuzzy matching) to {correct|appropriate|right} for typographical errors and misspellings. For {more|extra} {information|data|info} {about the|concerning the|in regards to the} {suggest|counsel|recommend} API, see Suggest {in the|within the} Search API. {When you|If you|Once you|Whenever you|While you} configure a suggester, {you must|it's essential to|you could|you have to|you need to|you should|you will need to} specify the {name|identify|title} of the {text|textual content} {field|area|discipline|subject} you {want to|need to|wish to} {search for|seek for} {possible|attainable|doable|potential} matches and {a unique|a novel|a singular} {name|identify|title} for the suggester. Fields used for suggestions {must be|have to be|should be} return enabled.





Only {the first|the primary} 512 bytes {of data|of information|of knowledge} in {the field|the sector|the sphere} are used to generate suggestions. Suggester names {must|should} {begin|start} with a letter and be {at least|a minimum of|at the least|at the very least|no less than|not less than} three and {no more than|not more than} {64|sixty four} characters {long|lengthy}. The suggester {name|identify|title} is specified {in the|within the} {query|question} string {when you|if you|once you|whenever you|while you} retrieve suggestions, so {it's best|it is best} {to use|to make use of} {short|brief|quick} names. The {name|identify|title} {score|rating} is reserved and {cannot be|can't be} used as a suggester {name|identify|title}. FuzzyMatching梇ou can set {the level|the extent} of fuzziness allowed when suggesting matches for a string to none, low, or {high|excessive}. With none, {the specified|the desired|the required} string is {treated|handled} as {an exact|a precise|an actual} prefix. With low, suggestions {must|should} differ from {the specified|the desired|the required} string by no {more than one|a couple of|multiple} character. With {high|excessive}, suggestions can differ by up {to two|to 2} characters. The default is none. SortExpression梇ou can configure this expression to compute a {score|rating} for {each|every} suggestion {to control|to manage|to regulate} how {they are|they're} sorted. To {sort|kind|type} suggestions {using|utilizing} a numeric {field|area|discipline|subject} or {existing|current|present} expression, {simply|merely} specify the {name|identify|title} of {the field|the sector|the sphere} or expression.





If no expression is configured for the suggester, the suggestions are sorted in alphabetical order. Note that an expression {defined|outlined} {within|inside} a suggester {cannot be|can't be} referenced in search requests or {other|different} expressions. If {want|need} {to use|to make use of} an expression for {other|different} {purposes|functions}, add it to your {domain|area} configuration and reference it by {name|identify|title} from the suggester. For {more|extra} {information about|details about} expressions, see Configuring Expressions. {If you want to|If you wish to} get suggestions from {multiple|a number of} {text|textual content} fields, you {define|outline} a suggester for {each|every} {field|area|discipline|subject} and submit separate suggestion requests to get matches from {each|every} suggester. {You can|You may|You possibly can|You'll be able to} configure up {to ten|to 10} suggesters. Suggesters can {consume|devour|eat} {significant|important|vital} {amounts|quantities} of {memory|reminiscence} and disk {space|area|house}, {particularly|notably|significantly} if {you use|you employ|you utilize} {text|textual content}-heavy {source|supply} fields and set fuzzy matching to {high|excessive}. Instead of configuring suggesters {to use|to make use of} all {possibilities|potentialities|prospects} from all {documents|paperwork}, consider indexing {the most popular|the most well-liked|the preferred} 1,000 or 10,000 search queries and configuring suggesters {to use|to make use of} {those|these}. {You can|You may|You possibly can|You'll be able to} {store|retailer} the queries in a separate Amazon CloudSearch index or in a {field|area|discipline|subject} used {only for|just for} suggestions.





{The easiest|The best|The simplest} {way to|approach to|method to|option to|solution to|strategy to|technique to} {define|outline} suggesters {is through|is thru} the Suggesters {page|web page} {in the|within the} Amazon CloudSearch console. {You can also|It's also possible to|You can even|You can too|You may also|You may as well|You too can} {define|outline} suggesters {using|utilizing} the AWS SDKs or AWS CLI. After you add a suggester to your search {domain|area}, {you must|it's essential to|you could|you have to|you need to|you should|you will need to} run indexing {before|earlier than} {you can use|you need to use|you should use|you should utilize} it to retrieve suggestions. As you add and delete {documents|paperwork}, {you must|it's essential to|you could|you have to|you need to|you should|you will need to} periodically rebuild your index to {update|replace} the suggestions. Suggestions {won't|will not} {reflect|mirror|replicate} added or deleted {documents|paperwork} {until|till} you {call|name} IndexDocuments. {You can|You may|You possibly can|You'll be able to} {easily|simply} add, {update|replace}, and delete suggesters {through|by|by means of|by way of|via} the Amazon CloudSearch console. 2. {In the|Within the} navigation pane, {click|click on} the {name|identify|title} of the {domain|area}, {and then|after which} {click|click on} the {domain|area}'s Suggesters {link|hyperlink}. 3. {In the|Within the} Suggesters pane, {click|click on} the Add {a new|a brand new} Suggester button. The button is {below|beneath|under} the {list|checklist|listing|record} of suggesters configured for the {domain|area}. 4. Enter {a name|a reputation} for {the new|the brand new} suggester {in the|within the} Name {field|area|discipline|subject}. 5. Specify the {text|textual content} {field|area|discipline|subject} you {want|need} {to use|to make use of} for suggestions {in the|within the} Source {field|area|discipline|subject}.





6. {If you want|If you need|If you would like|If you'd like|In order for you} {to include|to incorporate} suggestions that {correct|appropriate|right} for minor misspellings or typos, set the Fuzzy Matching {option to|choice to} low or {high|excessive}. When set to low, the suggestions {include|embody|embrace} {terms|phrases} that differ from the {user|consumer|person} {query|question} string by a single character. When set to {high|excessive}, the suggestions {include|embody|embrace} {terms|phrases} that differ by up {to two|to 2} characters. 7. {If you want|If you need|If you would like|If you'd like|In order for you} {to control|to manage|to regulate} how the suggestions are sorted, enter a numeric expression {in the|within the} Sort Expression {field|area|discipline|subject}. The expression can {simply|merely} be the {name|identify|title} of the numeric {field|area|discipline|subject} you {want|need} {to use|to make use of} to {sort|kind|type} the suggestions, the {name|identify|title} of an {existing|current|present} expression, or any {valid|legitimate} expression. For {more|extra} {information about|details about} expressions, see Configuring Expressions. 8. Click Submit {to save|to avoid wasting|to save lots of} your {changes|adjustments|modifications}. 9. {When you are|If you end up|If you find yourself|When you find yourself|When you're} {done|accomplished|achieved|carried out|completed|executed|finished|performed} configuring suggesters {for your|in your|on your|to your} search {domain|area}, {you must|it's essential to|you could|you have to|you need to|you should|you will need to} re-index your {domain|area} {before|earlier than} {you can use|you need to use|you should use|you should utilize} the suggesters. To run indexing, go to the {domain|area} dashboard {and click|and click on} the Run Indexing button on the {domain|area} dashboard.