Config to customize Autocomplete API response for both engines and data stores. Some fields are applicable to only one of them.
JSON representation |
---|
{
"name": string,
"matchingOrder": string,
"maxSuggestions": integer,
"minPrefixLength": integer,
"queryModel": string,
"queryFrequencyThreshold": integer,
"numUniqueUsersThreshold": integer,
"shouldServeContentSuggestions": boolean,
"filterPiiSuggestionsUsingDlp": boolean,
"enableMode": enum ( |
Fields | |
---|---|
name |
Required. Immutable. Fully qualified name |
matchingOrder |
The matching order for autocomplete suggestions, e.g., a query consisting of
Default value: |
maxSuggestions |
The maximum number of autocomplete suggestions returned per term. maxSuggestions must lie within the range of [1, 20]. If not set or set to 0, it will be set to the default of 20 suggestions. |
minPrefixLength |
The minimum number of characters needed to be typed in order to get suggestions. minPrefixLength must lie within the range of [1, 20]. If not set or set to 0, it will be set to the default of 1 character. |
queryModel |
The data model of query suggestions for serving. Currently supported values:
If query model is empty, the serving applies the "automatic" model by default. |
queryFrequencyThreshold |
This field is only meaningful for suggestions generated from user events or search history. If a query shows up less than this threshold, it may indicate that the query is rarely searched and thus will not be generated as a suggestion. This is field can be helpful for preventing PII queries becoming suggestions, as those queries are usually uniquely searched. If not set, the default value is 8 used in the generation pipeline. |
numUniqueUsersThreshold |
This field is only meaningful for suggestions generated from user events or search history, which may have user ids attached. If the number of unique users that have searched a query is less than this threshold, the query will not be generated as a suggestion. This is field can be helpful for preventing PII queries becoming suggestions, as those queries are usually uniquely searched. If not set, the default value is 3 used in the generation pipeline. |
shouldServeContentSuggestions |
Whether to generate and serve content suggestions. This allows for content suggestions to be served in addition to query suggestions. |
filterPiiSuggestionsUsingDlp |
If true, with best effort, try to detect and remove the suggestions containing certain types of PII information. This detection is performated by DLP under the hood. |
enableMode |
The enable mode of autocomplete generation pipelines. If this field is unset, the server behavior defaults to |
EnableMode
Specifies the enable mode of autocomplete generation pipelines.
Enums | |
---|---|
ENABLE_MODE_UNSPECIFIED |
When AutoComplete enable mode unspecified, it defaults to AUTOMATIC mode. |
AUTOMATIC |
AutoComplete will be enabled when the data store meets criteria. |
MANUAL |
AutoComplete will be enabled regardless of UCS data requirements. |