Google Cloud Native v0.30.0, Apr 14 23
Google Cloud Native v0.30.0, Apr 14 23
google-native.retail/v2beta.getControl
Explore with Pulumi AI
Gets a Control.
Using getControl
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getControl(args: GetControlArgs, opts?: InvokeOptions): Promise<GetControlResult>
function getControlOutput(args: GetControlOutputArgs, opts?: InvokeOptions): Output<GetControlResult>
def get_control(catalog_id: Optional[str] = None,
control_id: Optional[str] = None,
location: Optional[str] = None,
project: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetControlResult
def get_control_output(catalog_id: Optional[pulumi.Input[str]] = None,
control_id: Optional[pulumi.Input[str]] = None,
location: Optional[pulumi.Input[str]] = None,
project: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetControlResult]
func LookupControl(ctx *Context, args *LookupControlArgs, opts ...InvokeOption) (*LookupControlResult, error)
func LookupControlOutput(ctx *Context, args *LookupControlOutputArgs, opts ...InvokeOption) LookupControlResultOutput
> Note: This function is named LookupControl
in the Go SDK.
public static class GetControl
{
public static Task<GetControlResult> InvokeAsync(GetControlArgs args, InvokeOptions? opts = null)
public static Output<GetControlResult> Invoke(GetControlInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetControlResult> getControl(GetControlArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: google-native:retail/v2beta:getControl
arguments:
# arguments dictionary
The following arguments are supported:
- catalog_
id str - control_
id str - location str
- project str
getControl Result
The following output properties are available:
- Associated
Serving List<string>Config Ids List of serving config ids that are associated with this control in the same Catalog. Note the association is managed via the ServingConfig, this is an output only denormalized view.
- Display
Name string The human readable control display name. Used in Retail UI. This field must be a UTF-8 encoded string with a length limit of 128 characters. Otherwise, an INVALID_ARGUMENT error is thrown.
- Facet
Spec Pulumi.Google Native. Retail. V2Beta. Outputs. Google Cloud Retail V2beta Search Request Facet Spec Response A facet specification to perform faceted search. Note that this field is deprecated and will throw NOT_IMPLEMENTED if used for creating a control.
- Name string
Immutable. Fully qualified name
projects/*/locations/global/catalogs/*/controls/*
- Rule
Pulumi.
Google Native. Retail. V2Beta. Outputs. Google Cloud Retail V2beta Rule Response A rule control - a condition-action pair. Enacts a set action when the condition is triggered. For example: Boost "gShoe" when query full matches "Running Shoes".
- Search
Solution List<string>Use Case Specifies the use case for the control. Affects what condition fields can be set. Only settable by search controls. Will default to SEARCH_SOLUTION_USE_CASE_SEARCH if not specified. Currently only allow one search_solution_use_case per control.
- Solution
Types List<string> Immutable. The solution types that the control is used for. Currently we support setting only one type of solution at creation time. Only
SOLUTION_TYPE_SEARCH
value is supported at the moment. If no solution type is provided at creation time, will default to SOLUTION_TYPE_SEARCH.
- Associated
Serving []stringConfig Ids List of serving config ids that are associated with this control in the same Catalog. Note the association is managed via the ServingConfig, this is an output only denormalized view.
- Display
Name string The human readable control display name. Used in Retail UI. This field must be a UTF-8 encoded string with a length limit of 128 characters. Otherwise, an INVALID_ARGUMENT error is thrown.
- Facet
Spec GoogleCloud Retail V2beta Search Request Facet Spec Response A facet specification to perform faceted search. Note that this field is deprecated and will throw NOT_IMPLEMENTED if used for creating a control.
- Name string
Immutable. Fully qualified name
projects/*/locations/global/catalogs/*/controls/*
- Rule
Google
Cloud Retail V2beta Rule Response A rule control - a condition-action pair. Enacts a set action when the condition is triggered. For example: Boost "gShoe" when query full matches "Running Shoes".
- Search
Solution []stringUse Case Specifies the use case for the control. Affects what condition fields can be set. Only settable by search controls. Will default to SEARCH_SOLUTION_USE_CASE_SEARCH if not specified. Currently only allow one search_solution_use_case per control.
- Solution
Types []string Immutable. The solution types that the control is used for. Currently we support setting only one type of solution at creation time. Only
SOLUTION_TYPE_SEARCH
value is supported at the moment. If no solution type is provided at creation time, will default to SOLUTION_TYPE_SEARCH.
- associated
Serving List<String>Config Ids List of serving config ids that are associated with this control in the same Catalog. Note the association is managed via the ServingConfig, this is an output only denormalized view.
- display
Name String The human readable control display name. Used in Retail UI. This field must be a UTF-8 encoded string with a length limit of 128 characters. Otherwise, an INVALID_ARGUMENT error is thrown.
- facet
Spec GoogleCloud Retail V2beta Search Request Facet Spec Response A facet specification to perform faceted search. Note that this field is deprecated and will throw NOT_IMPLEMENTED if used for creating a control.
- name String
Immutable. Fully qualified name
projects/*/locations/global/catalogs/*/controls/*
- rule
Google
Cloud Retail V2beta Rule Response A rule control - a condition-action pair. Enacts a set action when the condition is triggered. For example: Boost "gShoe" when query full matches "Running Shoes".
- search
Solution List<String>Use Case Specifies the use case for the control. Affects what condition fields can be set. Only settable by search controls. Will default to SEARCH_SOLUTION_USE_CASE_SEARCH if not specified. Currently only allow one search_solution_use_case per control.
- solution
Types List<String> Immutable. The solution types that the control is used for. Currently we support setting only one type of solution at creation time. Only
SOLUTION_TYPE_SEARCH
value is supported at the moment. If no solution type is provided at creation time, will default to SOLUTION_TYPE_SEARCH.
- associated
Serving string[]Config Ids List of serving config ids that are associated with this control in the same Catalog. Note the association is managed via the ServingConfig, this is an output only denormalized view.
- display
Name string The human readable control display name. Used in Retail UI. This field must be a UTF-8 encoded string with a length limit of 128 characters. Otherwise, an INVALID_ARGUMENT error is thrown.
- facet
Spec GoogleCloud Retail V2beta Search Request Facet Spec Response A facet specification to perform faceted search. Note that this field is deprecated and will throw NOT_IMPLEMENTED if used for creating a control.
- name string
Immutable. Fully qualified name
projects/*/locations/global/catalogs/*/controls/*
- rule
Google
Cloud Retail V2beta Rule Response A rule control - a condition-action pair. Enacts a set action when the condition is triggered. For example: Boost "gShoe" when query full matches "Running Shoes".
- search
Solution string[]Use Case Specifies the use case for the control. Affects what condition fields can be set. Only settable by search controls. Will default to SEARCH_SOLUTION_USE_CASE_SEARCH if not specified. Currently only allow one search_solution_use_case per control.
- solution
Types string[] Immutable. The solution types that the control is used for. Currently we support setting only one type of solution at creation time. Only
SOLUTION_TYPE_SEARCH
value is supported at the moment. If no solution type is provided at creation time, will default to SOLUTION_TYPE_SEARCH.
- associated_
serving_ Sequence[str]config_ ids List of serving config ids that are associated with this control in the same Catalog. Note the association is managed via the ServingConfig, this is an output only denormalized view.
- display_
name str The human readable control display name. Used in Retail UI. This field must be a UTF-8 encoded string with a length limit of 128 characters. Otherwise, an INVALID_ARGUMENT error is thrown.
- facet_
spec GoogleCloud Retail V2beta Search Request Facet Spec Response A facet specification to perform faceted search. Note that this field is deprecated and will throw NOT_IMPLEMENTED if used for creating a control.
- name str
Immutable. Fully qualified name
projects/*/locations/global/catalogs/*/controls/*
- rule
Google
Cloud Retail V2beta Rule Response A rule control - a condition-action pair. Enacts a set action when the condition is triggered. For example: Boost "gShoe" when query full matches "Running Shoes".
- search_
solution_ Sequence[str]use_ case Specifies the use case for the control. Affects what condition fields can be set. Only settable by search controls. Will default to SEARCH_SOLUTION_USE_CASE_SEARCH if not specified. Currently only allow one search_solution_use_case per control.
- solution_
types Sequence[str] Immutable. The solution types that the control is used for. Currently we support setting only one type of solution at creation time. Only
SOLUTION_TYPE_SEARCH
value is supported at the moment. If no solution type is provided at creation time, will default to SOLUTION_TYPE_SEARCH.
- associated
Serving List<String>Config Ids List of serving config ids that are associated with this control in the same Catalog. Note the association is managed via the ServingConfig, this is an output only denormalized view.
- display
Name String The human readable control display name. Used in Retail UI. This field must be a UTF-8 encoded string with a length limit of 128 characters. Otherwise, an INVALID_ARGUMENT error is thrown.
- facet
Spec Property Map A facet specification to perform faceted search. Note that this field is deprecated and will throw NOT_IMPLEMENTED if used for creating a control.
- name String
Immutable. Fully qualified name
projects/*/locations/global/catalogs/*/controls/*
- rule Property Map
A rule control - a condition-action pair. Enacts a set action when the condition is triggered. For example: Boost "gShoe" when query full matches "Running Shoes".
- search
Solution List<String>Use Case Specifies the use case for the control. Affects what condition fields can be set. Only settable by search controls. Will default to SEARCH_SOLUTION_USE_CASE_SEARCH if not specified. Currently only allow one search_solution_use_case per control.
- solution
Types List<String> Immutable. The solution types that the control is used for. Currently we support setting only one type of solution at creation time. Only
SOLUTION_TYPE_SEARCH
value is supported at the moment. If no solution type is provided at creation time, will default to SOLUTION_TYPE_SEARCH.
Supporting Types
GoogleCloudRetailV2betaConditionQueryTermResponse
- Full
Match bool Whether this is supposed to be a full or partial match.
- Value string
The value of the term to match on. Value cannot be empty. Value can have at most 3 terms if specified as a partial match. Each space separated string is considered as one term. For example, "a b c" is 3 terms and allowed, but " a b c d" is 4 terms and not allowed for a partial match.
- Full
Match bool Whether this is supposed to be a full or partial match.
- Value string
The value of the term to match on. Value cannot be empty. Value can have at most 3 terms if specified as a partial match. Each space separated string is considered as one term. For example, "a b c" is 3 terms and allowed, but " a b c d" is 4 terms and not allowed for a partial match.
- full
Match Boolean Whether this is supposed to be a full or partial match.
- value String
The value of the term to match on. Value cannot be empty. Value can have at most 3 terms if specified as a partial match. Each space separated string is considered as one term. For example, "a b c" is 3 terms and allowed, but " a b c d" is 4 terms and not allowed for a partial match.
- full
Match boolean Whether this is supposed to be a full or partial match.
- value string
The value of the term to match on. Value cannot be empty. Value can have at most 3 terms if specified as a partial match. Each space separated string is considered as one term. For example, "a b c" is 3 terms and allowed, but " a b c d" is 4 terms and not allowed for a partial match.
- full_
match bool Whether this is supposed to be a full or partial match.
- value str
The value of the term to match on. Value cannot be empty. Value can have at most 3 terms if specified as a partial match. Each space separated string is considered as one term. For example, "a b c" is 3 terms and allowed, but " a b c d" is 4 terms and not allowed for a partial match.
- full
Match Boolean Whether this is supposed to be a full or partial match.
- value String
The value of the term to match on. Value cannot be empty. Value can have at most 3 terms if specified as a partial match. Each space separated string is considered as one term. For example, "a b c" is 3 terms and allowed, but " a b c d" is 4 terms and not allowed for a partial match.
GoogleCloudRetailV2betaConditionResponse
- Active
Time List<Pulumi.Range Google Native. Retail. V2Beta. Inputs. Google Cloud Retail V2beta Condition Time Range Response> Range of time(s) specifying when Condition is active. Condition true if any time range matches.
- Query
Terms List<Pulumi.Google Native. Retail. V2Beta. Inputs. Google Cloud Retail V2beta Condition Query Term Response> A list (up to 10 entries) of terms to match the query on. If not specified, match all queries. If many query terms are specified, the condition is matched if any of the terms is a match (i.e. using the OR operator).
- Active
Time []GoogleRange Cloud Retail V2beta Condition Time Range Response Range of time(s) specifying when Condition is active. Condition true if any time range matches.
- Query
Terms []GoogleCloud Retail V2beta Condition Query Term Response A list (up to 10 entries) of terms to match the query on. If not specified, match all queries. If many query terms are specified, the condition is matched if any of the terms is a match (i.e. using the OR operator).
- active
Time List<GoogleRange Cloud Retail V2beta Condition Time Range Response> Range of time(s) specifying when Condition is active. Condition true if any time range matches.
- query
Terms List<GoogleCloud Retail V2beta Condition Query Term Response> A list (up to 10 entries) of terms to match the query on. If not specified, match all queries. If many query terms are specified, the condition is matched if any of the terms is a match (i.e. using the OR operator).
- active
Time GoogleRange Cloud Retail V2beta Condition Time Range Response[] Range of time(s) specifying when Condition is active. Condition true if any time range matches.
- query
Terms GoogleCloud Retail V2beta Condition Query Term Response[] A list (up to 10 entries) of terms to match the query on. If not specified, match all queries. If many query terms are specified, the condition is matched if any of the terms is a match (i.e. using the OR operator).
- active_
time_ Sequence[Googlerange Cloud Retail V2beta Condition Time Range Response] Range of time(s) specifying when Condition is active. Condition true if any time range matches.
- query_
terms Sequence[GoogleCloud Retail V2beta Condition Query Term Response] A list (up to 10 entries) of terms to match the query on. If not specified, match all queries. If many query terms are specified, the condition is matched if any of the terms is a match (i.e. using the OR operator).
- active
Time List<Property Map>Range Range of time(s) specifying when Condition is active. Condition true if any time range matches.
- query
Terms List<Property Map> A list (up to 10 entries) of terms to match the query on. If not specified, match all queries. If many query terms are specified, the condition is matched if any of the terms is a match (i.e. using the OR operator).
GoogleCloudRetailV2betaConditionTimeRangeResponse
- end_
time str End of time range. Range is inclusive.
- start_
time str Start of time range. Range is inclusive.
GoogleCloudRetailV2betaIntervalResponse
- Exclusive
Maximum double Exclusive upper bound.
- Exclusive
Minimum double Exclusive lower bound.
- Maximum double
Inclusive upper bound.
- Minimum double
Inclusive lower bound.
- Exclusive
Maximum float64 Exclusive upper bound.
- Exclusive
Minimum float64 Exclusive lower bound.
- Maximum float64
Inclusive upper bound.
- Minimum float64
Inclusive lower bound.
- exclusive
Maximum Double Exclusive upper bound.
- exclusive
Minimum Double Exclusive lower bound.
- maximum Double
Inclusive upper bound.
- minimum Double
Inclusive lower bound.
- exclusive
Maximum number Exclusive upper bound.
- exclusive
Minimum number Exclusive lower bound.
- maximum number
Inclusive upper bound.
- minimum number
Inclusive lower bound.
- exclusive_
maximum float Exclusive upper bound.
- exclusive_
minimum float Exclusive lower bound.
- maximum float
Inclusive upper bound.
- minimum float
Inclusive lower bound.
- exclusive
Maximum Number Exclusive upper bound.
- exclusive
Minimum Number Exclusive lower bound.
- maximum Number
Inclusive upper bound.
- minimum Number
Inclusive lower bound.
GoogleCloudRetailV2betaRuleBoostActionResponse
- Boost double
Strength of the condition boost, which must be in [-1, 1]. Negative boost means demotion. Default is 0.0. Setting to 1.0 gives the item a big promotion. However, it does not necessarily mean that the boosted item will be the top result at all times, nor that other items will be excluded. Results could still be shown even when none of them matches the condition. And results that are significantly more relevant to the search query can still trump your heavily favored but irrelevant items. Setting to -1.0 gives the item a big demotion. However, results that are deeply relevant might still be shown. The item will have an upstream battle to get a fairly high ranking, but it is not blocked out completely. Setting to 0.0 means no boost applied. The boosting condition is ignored.
- Products
Filter string The filter can have a max size of 5000 characters. An expression which specifies which products to apply an action to. The syntax and supported fields are the same as a filter expression. See SearchRequest.filter for detail syntax and limitations. Examples: * To boost products with product ID "product_1" or "product_2", and color "Red" or "Blue": *(id: ANY("product_1", "product_2")) * *AND * *(colorFamilies: ANY("Red", "Blue")) *
- Boost float64
Strength of the condition boost, which must be in [-1, 1]. Negative boost means demotion. Default is 0.0. Setting to 1.0 gives the item a big promotion. However, it does not necessarily mean that the boosted item will be the top result at all times, nor that other items will be excluded. Results could still be shown even when none of them matches the condition. And results that are significantly more relevant to the search query can still trump your heavily favored but irrelevant items. Setting to -1.0 gives the item a big demotion. However, results that are deeply relevant might still be shown. The item will have an upstream battle to get a fairly high ranking, but it is not blocked out completely. Setting to 0.0 means no boost applied. The boosting condition is ignored.
- Products
Filter string The filter can have a max size of 5000 characters. An expression which specifies which products to apply an action to. The syntax and supported fields are the same as a filter expression. See SearchRequest.filter for detail syntax and limitations. Examples: * To boost products with product ID "product_1" or "product_2", and color "Red" or "Blue": *(id: ANY("product_1", "product_2")) * *AND * *(colorFamilies: ANY("Red", "Blue")) *
- boost Double
Strength of the condition boost, which must be in [-1, 1]. Negative boost means demotion. Default is 0.0. Setting to 1.0 gives the item a big promotion. However, it does not necessarily mean that the boosted item will be the top result at all times, nor that other items will be excluded. Results could still be shown even when none of them matches the condition. And results that are significantly more relevant to the search query can still trump your heavily favored but irrelevant items. Setting to -1.0 gives the item a big demotion. However, results that are deeply relevant might still be shown. The item will have an upstream battle to get a fairly high ranking, but it is not blocked out completely. Setting to 0.0 means no boost applied. The boosting condition is ignored.
- products
Filter String The filter can have a max size of 5000 characters. An expression which specifies which products to apply an action to. The syntax and supported fields are the same as a filter expression. See SearchRequest.filter for detail syntax and limitations. Examples: * To boost products with product ID "product_1" or "product_2", and color "Red" or "Blue": *(id: ANY("product_1", "product_2")) * *AND * *(colorFamilies: ANY("Red", "Blue")) *
- boost number
Strength of the condition boost, which must be in [-1, 1]. Negative boost means demotion. Default is 0.0. Setting to 1.0 gives the item a big promotion. However, it does not necessarily mean that the boosted item will be the top result at all times, nor that other items will be excluded. Results could still be shown even when none of them matches the condition. And results that are significantly more relevant to the search query can still trump your heavily favored but irrelevant items. Setting to -1.0 gives the item a big demotion. However, results that are deeply relevant might still be shown. The item will have an upstream battle to get a fairly high ranking, but it is not blocked out completely. Setting to 0.0 means no boost applied. The boosting condition is ignored.
- products
Filter string The filter can have a max size of 5000 characters. An expression which specifies which products to apply an action to. The syntax and supported fields are the same as a filter expression. See SearchRequest.filter for detail syntax and limitations. Examples: * To boost products with product ID "product_1" or "product_2", and color "Red" or "Blue": *(id: ANY("product_1", "product_2")) * *AND * *(colorFamilies: ANY("Red", "Blue")) *
- boost float
Strength of the condition boost, which must be in [-1, 1]. Negative boost means demotion. Default is 0.0. Setting to 1.0 gives the item a big promotion. However, it does not necessarily mean that the boosted item will be the top result at all times, nor that other items will be excluded. Results could still be shown even when none of them matches the condition. And results that are significantly more relevant to the search query can still trump your heavily favored but irrelevant items. Setting to -1.0 gives the item a big demotion. However, results that are deeply relevant might still be shown. The item will have an upstream battle to get a fairly high ranking, but it is not blocked out completely. Setting to 0.0 means no boost applied. The boosting condition is ignored.
- products_
filter str The filter can have a max size of 5000 characters. An expression which specifies which products to apply an action to. The syntax and supported fields are the same as a filter expression. See SearchRequest.filter for detail syntax and limitations. Examples: * To boost products with product ID "product_1" or "product_2", and color "Red" or "Blue": *(id: ANY("product_1", "product_2")) * *AND * *(colorFamilies: ANY("Red", "Blue")) *
- boost Number
Strength of the condition boost, which must be in [-1, 1]. Negative boost means demotion. Default is 0.0. Setting to 1.0 gives the item a big promotion. However, it does not necessarily mean that the boosted item will be the top result at all times, nor that other items will be excluded. Results could still be shown even when none of them matches the condition. And results that are significantly more relevant to the search query can still trump your heavily favored but irrelevant items. Setting to -1.0 gives the item a big demotion. However, results that are deeply relevant might still be shown. The item will have an upstream battle to get a fairly high ranking, but it is not blocked out completely. Setting to 0.0 means no boost applied. The boosting condition is ignored.
- products
Filter String The filter can have a max size of 5000 characters. An expression which specifies which products to apply an action to. The syntax and supported fields are the same as a filter expression. See SearchRequest.filter for detail syntax and limitations. Examples: * To boost products with product ID "product_1" or "product_2", and color "Red" or "Blue": *(id: ANY("product_1", "product_2")) * *AND * *(colorFamilies: ANY("Red", "Blue")) *
GoogleCloudRetailV2betaRuleDoNotAssociateActionResponse
- Do
Not List<string>Associate Terms Cannot contain duplicates or the query term. Can specify up to 100 terms.
- Query
Terms List<string> Terms from the search query. Will not consider do_not_associate_terms for search if in search query. Can specify up to 100 terms.
- Terms List<string>
Will be [deprecated = true] post migration;
- Do
Not []stringAssociate Terms Cannot contain duplicates or the query term. Can specify up to 100 terms.
- Query
Terms []string Terms from the search query. Will not consider do_not_associate_terms for search if in search query. Can specify up to 100 terms.
- Terms []string
Will be [deprecated = true] post migration;
- do
Not List<String>Associate Terms Cannot contain duplicates or the query term. Can specify up to 100 terms.
- query
Terms List<String> Terms from the search query. Will not consider do_not_associate_terms for search if in search query. Can specify up to 100 terms.
- terms List<String>
Will be [deprecated = true] post migration;
- do
Not string[]Associate Terms Cannot contain duplicates or the query term. Can specify up to 100 terms.
- query
Terms string[] Terms from the search query. Will not consider do_not_associate_terms for search if in search query. Can specify up to 100 terms.
- terms string[]
Will be [deprecated = true] post migration;
- do_
not_ Sequence[str]associate_ terms Cannot contain duplicates or the query term. Can specify up to 100 terms.
- query_
terms Sequence[str] Terms from the search query. Will not consider do_not_associate_terms for search if in search query. Can specify up to 100 terms.
- terms Sequence[str]
Will be [deprecated = true] post migration;
- do
Not List<String>Associate Terms Cannot contain duplicates or the query term. Can specify up to 100 terms.
- query
Terms List<String> Terms from the search query. Will not consider do_not_associate_terms for search if in search query. Can specify up to 100 terms.
- terms List<String>
Will be [deprecated = true] post migration;
GoogleCloudRetailV2betaRuleFilterActionResponse
- Filter string
A filter to apply on the matching condition results. Supported features: * filter must be set. * Filter syntax is identical to SearchRequest.filter. See more details at the Retail Search user guide. * To filter products with product ID "product_1" or "product_2", and color "Red" or "Blue": *(id: ANY("product_1", "product_2")) * *AND * *(colorFamilies: ANY("Red", "Blue")) *
- Filter string
A filter to apply on the matching condition results. Supported features: * filter must be set. * Filter syntax is identical to SearchRequest.filter. See more details at the Retail Search user guide. * To filter products with product ID "product_1" or "product_2", and color "Red" or "Blue": *(id: ANY("product_1", "product_2")) * *AND * *(colorFamilies: ANY("Red", "Blue")) *
- filter String
A filter to apply on the matching condition results. Supported features: * filter must be set. * Filter syntax is identical to SearchRequest.filter. See more details at the Retail Search user guide. * To filter products with product ID "product_1" or "product_2", and color "Red" or "Blue": *(id: ANY("product_1", "product_2")) * *AND * *(colorFamilies: ANY("Red", "Blue")) *
- filter string
A filter to apply on the matching condition results. Supported features: * filter must be set. * Filter syntax is identical to SearchRequest.filter. See more details at the Retail Search user guide. * To filter products with product ID "product_1" or "product_2", and color "Red" or "Blue": *(id: ANY("product_1", "product_2")) * *AND * *(colorFamilies: ANY("Red", "Blue")) *
- filter str
A filter to apply on the matching condition results. Supported features: * filter must be set. * Filter syntax is identical to SearchRequest.filter. See more details at the Retail Search user guide. * To filter products with product ID "product_1" or "product_2", and color "Red" or "Blue": *(id: ANY("product_1", "product_2")) * *AND * *(colorFamilies: ANY("Red", "Blue")) *
- filter String
A filter to apply on the matching condition results. Supported features: * filter must be set. * Filter syntax is identical to SearchRequest.filter. See more details at the Retail Search user guide. * To filter products with product ID "product_1" or "product_2", and color "Red" or "Blue": *(id: ANY("product_1", "product_2")) * *AND * *(colorFamilies: ANY("Red", "Blue")) *
GoogleCloudRetailV2betaRuleIgnoreActionResponse
- Ignore
Terms List<string> Terms to ignore in the search query.
- Ignore
Terms []string Terms to ignore in the search query.
- ignore
Terms List<String> Terms to ignore in the search query.
- ignore
Terms string[] Terms to ignore in the search query.
- ignore_
terms Sequence[str] Terms to ignore in the search query.
- ignore
Terms List<String> Terms to ignore in the search query.
GoogleCloudRetailV2betaRuleOnewaySynonymsActionResponse
- Oneway
Terms List<string> Will be [deprecated = true] post migration;
- Query
Terms List<string> Terms from the search query. Will treat synonyms as their synonyms. Not themselves synonyms of the synonyms. Can specify up to 100 terms.
- Synonyms List<string>
Defines a set of synonyms. Cannot contain duplicates. Can specify up to 100 synonyms.
- Oneway
Terms []string Will be [deprecated = true] post migration;
- Query
Terms []string Terms from the search query. Will treat synonyms as their synonyms. Not themselves synonyms of the synonyms. Can specify up to 100 terms.
- Synonyms []string
Defines a set of synonyms. Cannot contain duplicates. Can specify up to 100 synonyms.
- oneway
Terms List<String> Will be [deprecated = true] post migration;
- query
Terms List<String> Terms from the search query. Will treat synonyms as their synonyms. Not themselves synonyms of the synonyms. Can specify up to 100 terms.
- synonyms List<String>
Defines a set of synonyms. Cannot contain duplicates. Can specify up to 100 synonyms.
- oneway
Terms string[] Will be [deprecated = true] post migration;
- query
Terms string[] Terms from the search query. Will treat synonyms as their synonyms. Not themselves synonyms of the synonyms. Can specify up to 100 terms.
- synonyms string[]
Defines a set of synonyms. Cannot contain duplicates. Can specify up to 100 synonyms.
- oneway_
terms Sequence[str] Will be [deprecated = true] post migration;
- query_
terms Sequence[str] Terms from the search query. Will treat synonyms as their synonyms. Not themselves synonyms of the synonyms. Can specify up to 100 terms.
- synonyms Sequence[str]
Defines a set of synonyms. Cannot contain duplicates. Can specify up to 100 synonyms.
- oneway
Terms List<String> Will be [deprecated = true] post migration;
- query
Terms List<String> Terms from the search query. Will treat synonyms as their synonyms. Not themselves synonyms of the synonyms. Can specify up to 100 terms.
- synonyms List<String>
Defines a set of synonyms. Cannot contain duplicates. Can specify up to 100 synonyms.
GoogleCloudRetailV2betaRuleRedirectActionResponse
- Redirect
Uri string URL must have length equal or less than 2000 characters.
- Redirect
Uri string URL must have length equal or less than 2000 characters.
- redirect
Uri String URL must have length equal or less than 2000 characters.
- redirect
Uri string URL must have length equal or less than 2000 characters.
- redirect_
uri str URL must have length equal or less than 2000 characters.
- redirect
Uri String URL must have length equal or less than 2000 characters.
GoogleCloudRetailV2betaRuleReplacementActionResponse
- Query
Terms List<string> Terms from the search query. Will be replaced by replacement term. Can specify up to 100 terms.
- Replacement
Term string Term that will be used for replacement.
- Term string
Will be [deprecated = true] post migration;
- Query
Terms []string Terms from the search query. Will be replaced by replacement term. Can specify up to 100 terms.
- Replacement
Term string Term that will be used for replacement.
- Term string
Will be [deprecated = true] post migration;
- query
Terms List<String> Terms from the search query. Will be replaced by replacement term. Can specify up to 100 terms.
- replacement
Term String Term that will be used for replacement.
- term String
Will be [deprecated = true] post migration;
- query
Terms string[] Terms from the search query. Will be replaced by replacement term. Can specify up to 100 terms.
- replacement
Term string Term that will be used for replacement.
- term string
Will be [deprecated = true] post migration;
- query_
terms Sequence[str] Terms from the search query. Will be replaced by replacement term. Can specify up to 100 terms.
- replacement_
term str Term that will be used for replacement.
- term str
Will be [deprecated = true] post migration;
- query
Terms List<String> Terms from the search query. Will be replaced by replacement term. Can specify up to 100 terms.
- replacement
Term String Term that will be used for replacement.
- term String
Will be [deprecated = true] post migration;
GoogleCloudRetailV2betaRuleResponse
- Boost
Action Pulumi.Google Native. Retail. V2Beta. Inputs. Google Cloud Retail V2beta Rule Boost Action Response A boost action.
- Condition
Pulumi.
Google Native. Retail. V2Beta. Inputs. Google Cloud Retail V2beta Condition Response The condition that triggers the rule. If the condition is empty, the rule will always apply.
- Do
Not Pulumi.Associate Action Google Native. Retail. V2Beta. Inputs. Google Cloud Retail V2beta Rule Do Not Associate Action Response Prevents term from being associated with other terms.
- Filter
Action Pulumi.Google Native. Retail. V2Beta. Inputs. Google Cloud Retail V2beta Rule Filter Action Response Filters results.
- Ignore
Action Pulumi.Google Native. Retail. V2Beta. Inputs. Google Cloud Retail V2beta Rule Ignore Action Response Ignores specific terms from query during search.
- Oneway
Synonyms Pulumi.Action Google Native. Retail. V2Beta. Inputs. Google Cloud Retail V2beta Rule Oneway Synonyms Action Response Treats specific term as a synonym with a group of terms. Group of terms will not be treated as synonyms with the specific term.
- Redirect
Action Pulumi.Google Native. Retail. V2Beta. Inputs. Google Cloud Retail V2beta Rule Redirect Action Response Redirects a shopper to a specific page.
- Replacement
Action Pulumi.Google Native. Retail. V2Beta. Inputs. Google Cloud Retail V2beta Rule Replacement Action Response Replaces specific terms in the query.
- Twoway
Synonyms Pulumi.Action Google Native. Retail. V2Beta. Inputs. Google Cloud Retail V2beta Rule Twoway Synonyms Action Response Treats a set of terms as synonyms of one another.
- Boost
Action GoogleCloud Retail V2beta Rule Boost Action Response A boost action.
- Condition
Google
Cloud Retail V2beta Condition Response The condition that triggers the rule. If the condition is empty, the rule will always apply.
- Do
Not GoogleAssociate Action Cloud Retail V2beta Rule Do Not Associate Action Response Prevents term from being associated with other terms.
- Filter
Action GoogleCloud Retail V2beta Rule Filter Action Response Filters results.
- Ignore
Action GoogleCloud Retail V2beta Rule Ignore Action Response Ignores specific terms from query during search.
- Oneway
Synonyms GoogleAction Cloud Retail V2beta Rule Oneway Synonyms Action Response Treats specific term as a synonym with a group of terms. Group of terms will not be treated as synonyms with the specific term.
- Redirect
Action GoogleCloud Retail V2beta Rule Redirect Action Response Redirects a shopper to a specific page.
- Replacement
Action GoogleCloud Retail V2beta Rule Replacement Action Response Replaces specific terms in the query.
- Twoway
Synonyms GoogleAction Cloud Retail V2beta Rule Twoway Synonyms Action Response Treats a set of terms as synonyms of one another.
- boost
Action GoogleCloud Retail V2beta Rule Boost Action Response A boost action.
- condition
Google
Cloud Retail V2beta Condition Response The condition that triggers the rule. If the condition is empty, the rule will always apply.
- do
Not GoogleAssociate Action Cloud Retail V2beta Rule Do Not Associate Action Response Prevents term from being associated with other terms.
- filter
Action GoogleCloud Retail V2beta Rule Filter Action Response Filters results.
- ignore
Action GoogleCloud Retail V2beta Rule Ignore Action Response Ignores specific terms from query during search.
- oneway
Synonyms GoogleAction Cloud Retail V2beta Rule Oneway Synonyms Action Response Treats specific term as a synonym with a group of terms. Group of terms will not be treated as synonyms with the specific term.
- redirect
Action GoogleCloud Retail V2beta Rule Redirect Action Response Redirects a shopper to a specific page.
- replacement
Action GoogleCloud Retail V2beta Rule Replacement Action Response Replaces specific terms in the query.
- twoway
Synonyms GoogleAction Cloud Retail V2beta Rule Twoway Synonyms Action Response Treats a set of terms as synonyms of one another.
- boost
Action GoogleCloud Retail V2beta Rule Boost Action Response A boost action.
- condition
Google
Cloud Retail V2beta Condition Response The condition that triggers the rule. If the condition is empty, the rule will always apply.
- do
Not GoogleAssociate Action Cloud Retail V2beta Rule Do Not Associate Action Response Prevents term from being associated with other terms.
- filter
Action GoogleCloud Retail V2beta Rule Filter Action Response Filters results.
- ignore
Action GoogleCloud Retail V2beta Rule Ignore Action Response Ignores specific terms from query during search.
- oneway
Synonyms GoogleAction Cloud Retail V2beta Rule Oneway Synonyms Action Response Treats specific term as a synonym with a group of terms. Group of terms will not be treated as synonyms with the specific term.
- redirect
Action GoogleCloud Retail V2beta Rule Redirect Action Response Redirects a shopper to a specific page.
- replacement
Action GoogleCloud Retail V2beta Rule Replacement Action Response Replaces specific terms in the query.
- twoway
Synonyms GoogleAction Cloud Retail V2beta Rule Twoway Synonyms Action Response Treats a set of terms as synonyms of one another.
- boost_
action GoogleCloud Retail V2beta Rule Boost Action Response A boost action.
- condition
Google
Cloud Retail V2beta Condition Response The condition that triggers the rule. If the condition is empty, the rule will always apply.
- do_
not_ Googleassociate_ action Cloud Retail V2beta Rule Do Not Associate Action Response Prevents term from being associated with other terms.
- filter_
action GoogleCloud Retail V2beta Rule Filter Action Response Filters results.
- ignore_
action GoogleCloud Retail V2beta Rule Ignore Action Response Ignores specific terms from query during search.
- oneway_
synonyms_ Googleaction Cloud Retail V2beta Rule Oneway Synonyms Action Response Treats specific term as a synonym with a group of terms. Group of terms will not be treated as synonyms with the specific term.
- redirect_
action GoogleCloud Retail V2beta Rule Redirect Action Response Redirects a shopper to a specific page.
- replacement_
action GoogleCloud Retail V2beta Rule Replacement Action Response Replaces specific terms in the query.
- twoway_
synonyms_ Googleaction Cloud Retail V2beta Rule Twoway Synonyms Action Response Treats a set of terms as synonyms of one another.
- boost
Action Property Map A boost action.
- condition Property Map
The condition that triggers the rule. If the condition is empty, the rule will always apply.
- do
Not Property MapAssociate Action Prevents term from being associated with other terms.
- filter
Action Property Map Filters results.
- ignore
Action Property Map Ignores specific terms from query during search.
- oneway
Synonyms Property MapAction Treats specific term as a synonym with a group of terms. Group of terms will not be treated as synonyms with the specific term.
- redirect
Action Property Map Redirects a shopper to a specific page.
- replacement
Action Property Map Replaces specific terms in the query.
- twoway
Synonyms Property MapAction Treats a set of terms as synonyms of one another.
GoogleCloudRetailV2betaRuleTwowaySynonymsActionResponse
- Synonyms List<string>
Defines a set of synonyms. Can specify up to 100 synonyms. Must specify at least 2 synonyms.
- Synonyms []string
Defines a set of synonyms. Can specify up to 100 synonyms. Must specify at least 2 synonyms.
- synonyms List<String>
Defines a set of synonyms. Can specify up to 100 synonyms. Must specify at least 2 synonyms.
- synonyms string[]
Defines a set of synonyms. Can specify up to 100 synonyms. Must specify at least 2 synonyms.
- synonyms Sequence[str]
Defines a set of synonyms. Can specify up to 100 synonyms. Must specify at least 2 synonyms.
- synonyms List<String>
Defines a set of synonyms. Can specify up to 100 synonyms. Must specify at least 2 synonyms.
GoogleCloudRetailV2betaSearchRequestFacetSpecFacetKeyResponse
- Case
Insensitive bool True to make facet keys case insensitive when getting faceting values with prefixes or contains; false otherwise.
- Contains List<string>
Only get facet values that contains the given strings. For example, suppose "categories" has three values "Women > Shoe", "Women > Dress" and "Men > Shoe". If set "contains" to "Shoe", the "categories" facet will give only "Women > Shoe" and "Men > Shoe". Only supported on textual fields. Maximum is 10.
- Intervals
List<Pulumi.
Google Native. Retail. V2Beta. Inputs. Google Cloud Retail V2beta Interval Response> For all numerical facet keys that appear in the list of products from the catalog, the percentiles 0, 10, 30, 50, 70, 90 and 100 are computed from their distribution weekly. If the model assigns a high score to a numerical facet key and its intervals are not specified in the search request, these percentiles will become the bounds for its intervals and will be returned in the response. If the facet key intervals are specified in the request, then the specified intervals will be returned instead.
- Key string
Supported textual and numerical facet keys in Product object, over which the facet values are computed. Facet key is case-sensitive. Allowed facet keys when FacetKey.query is not specified: * textual_field = * "brands" * "categories" * "genders" * "ageGroups" * "availability" * "colorFamilies" * "colors" * "sizes" * "materials" * "patterns" * "conditions" * "attributes.key" * "pickupInStore" * "shipToStore" * "sameDayDelivery" * "nextDayDelivery" * "customFulfillment1" * "customFulfillment2" * "customFulfillment3" * "customFulfillment4" * "customFulfillment5" * "inventory(place_id,attributes.key)" * numerical_field = * "price" * "discount" * "rating" * "ratingCount" * "attributes.key" * "inventory(place_id,price)" * "inventory(place_id,original_price)" * "inventory(place_id,attributes.key)"
- Order
By string The order in which SearchResponse.Facet.values are returned. Allowed values are: * "count desc", which means order by SearchResponse.Facet.values.count descending. * "value desc", which means order by SearchResponse.Facet.values.value descending. Only applies to textual facets. If not set, textual values are sorted in natural order; numerical intervals are sorted in the order given by FacetSpec.FacetKey.intervals; FulfillmentInfo.place_ids are sorted in the order given by FacetSpec.FacetKey.restricted_values.
- Prefixes List<string>
Only get facet values that start with the given string prefix. For example, suppose "categories" has three values "Women > Shoe", "Women > Dress" and "Men > Shoe". If set "prefixes" to "Women", the "categories" facet will give only "Women > Shoe" and "Women > Dress". Only supported on textual fields. Maximum is 10.
- Query string
The query that is used to compute facet for the given facet key. When provided, it will override the default behavior of facet computation. The query syntax is the same as a filter expression. See SearchRequest.filter for detail syntax and limitations. Notice that there is no limitation on FacetKey.key when query is specified. In the response, SearchResponse.Facet.values.value will be always "1" and SearchResponse.Facet.values.count will be the number of results that match the query. For example, you can set a customized facet for "shipToStore", where FacetKey.key is "customizedShipToStore", and FacetKey.query is "availability: ANY("IN_STOCK") AND shipToStore: ANY("123")". Then the facet will count the products that are both in stock and ship to store "123".
- Restricted
Values List<string> Only get facet for the given restricted values. For example, when using "pickupInStore" as key and set restricted values to ["store123", "store456"], only facets for "store123" and "store456" are returned. Only supported on predefined textual fields, custom textual attributes and fulfillments. Maximum is 20. Must be set for the fulfillment facet keys: * pickupInStore * shipToStore * sameDayDelivery * nextDayDelivery * customFulfillment1 * customFulfillment2 * customFulfillment3 * customFulfillment4 * customFulfillment5
- Return
Min boolMax Returns the min and max value for each numerical facet intervals. Ignored for textual facets.
- Case
Insensitive bool True to make facet keys case insensitive when getting faceting values with prefixes or contains; false otherwise.
- Contains []string
Only get facet values that contains the given strings. For example, suppose "categories" has three values "Women > Shoe", "Women > Dress" and "Men > Shoe". If set "contains" to "Shoe", the "categories" facet will give only "Women > Shoe" and "Men > Shoe". Only supported on textual fields. Maximum is 10.
- Intervals
[]Google
Cloud Retail V2beta Interval Response For all numerical facet keys that appear in the list of products from the catalog, the percentiles 0, 10, 30, 50, 70, 90 and 100 are computed from their distribution weekly. If the model assigns a high score to a numerical facet key and its intervals are not specified in the search request, these percentiles will become the bounds for its intervals and will be returned in the response. If the facet key intervals are specified in the request, then the specified intervals will be returned instead.
- Key string
Supported textual and numerical facet keys in Product object, over which the facet values are computed. Facet key is case-sensitive. Allowed facet keys when FacetKey.query is not specified: * textual_field = * "brands" * "categories" * "genders" * "ageGroups" * "availability" * "colorFamilies" * "colors" * "sizes" * "materials" * "patterns" * "conditions" * "attributes.key" * "pickupInStore" * "shipToStore" * "sameDayDelivery" * "nextDayDelivery" * "customFulfillment1" * "customFulfillment2" * "customFulfillment3" * "customFulfillment4" * "customFulfillment5" * "inventory(place_id,attributes.key)" * numerical_field = * "price" * "discount" * "rating" * "ratingCount" * "attributes.key" * "inventory(place_id,price)" * "inventory(place_id,original_price)" * "inventory(place_id,attributes.key)"
- Order
By string The order in which SearchResponse.Facet.values are returned. Allowed values are: * "count desc", which means order by SearchResponse.Facet.values.count descending. * "value desc", which means order by SearchResponse.Facet.values.value descending. Only applies to textual facets. If not set, textual values are sorted in natural order; numerical intervals are sorted in the order given by FacetSpec.FacetKey.intervals; FulfillmentInfo.place_ids are sorted in the order given by FacetSpec.FacetKey.restricted_values.
- Prefixes []string
Only get facet values that start with the given string prefix. For example, suppose "categories" has three values "Women > Shoe", "Women > Dress" and "Men > Shoe". If set "prefixes" to "Women", the "categories" facet will give only "Women > Shoe" and "Women > Dress". Only supported on textual fields. Maximum is 10.
- Query string
The query that is used to compute facet for the given facet key. When provided, it will override the default behavior of facet computation. The query syntax is the same as a filter expression. See SearchRequest.filter for detail syntax and limitations. Notice that there is no limitation on FacetKey.key when query is specified. In the response, SearchResponse.Facet.values.value will be always "1" and SearchResponse.Facet.values.count will be the number of results that match the query. For example, you can set a customized facet for "shipToStore", where FacetKey.key is "customizedShipToStore", and FacetKey.query is "availability: ANY("IN_STOCK") AND shipToStore: ANY("123")". Then the facet will count the products that are both in stock and ship to store "123".
- Restricted
Values []string Only get facet for the given restricted values. For example, when using "pickupInStore" as key and set restricted values to ["store123", "store456"], only facets for "store123" and "store456" are returned. Only supported on predefined textual fields, custom textual attributes and fulfillments. Maximum is 20. Must be set for the fulfillment facet keys: * pickupInStore * shipToStore * sameDayDelivery * nextDayDelivery * customFulfillment1 * customFulfillment2 * customFulfillment3 * customFulfillment4 * customFulfillment5
- Return
Min boolMax Returns the min and max value for each numerical facet intervals. Ignored for textual facets.
- case
Insensitive Boolean True to make facet keys case insensitive when getting faceting values with prefixes or contains; false otherwise.
- contains List<String>
Only get facet values that contains the given strings. For example, suppose "categories" has three values "Women > Shoe", "Women > Dress" and "Men > Shoe". If set "contains" to "Shoe", the "categories" facet will give only "Women > Shoe" and "Men > Shoe". Only supported on textual fields. Maximum is 10.
- intervals
List<Google
Cloud Retail V2beta Interval Response> For all numerical facet keys that appear in the list of products from the catalog, the percentiles 0, 10, 30, 50, 70, 90 and 100 are computed from their distribution weekly. If the model assigns a high score to a numerical facet key and its intervals are not specified in the search request, these percentiles will become the bounds for its intervals and will be returned in the response. If the facet key intervals are specified in the request, then the specified intervals will be returned instead.
- key String
Supported textual and numerical facet keys in Product object, over which the facet values are computed. Facet key is case-sensitive. Allowed facet keys when FacetKey.query is not specified: * textual_field = * "brands" * "categories" * "genders" * "ageGroups" * "availability" * "colorFamilies" * "colors" * "sizes" * "materials" * "patterns" * "conditions" * "attributes.key" * "pickupInStore" * "shipToStore" * "sameDayDelivery" * "nextDayDelivery" * "customFulfillment1" * "customFulfillment2" * "customFulfillment3" * "customFulfillment4" * "customFulfillment5" * "inventory(place_id,attributes.key)" * numerical_field = * "price" * "discount" * "rating" * "ratingCount" * "attributes.key" * "inventory(place_id,price)" * "inventory(place_id,original_price)" * "inventory(place_id,attributes.key)"
- order
By String The order in which SearchResponse.Facet.values are returned. Allowed values are: * "count desc", which means order by SearchResponse.Facet.values.count descending. * "value desc", which means order by SearchResponse.Facet.values.value descending. Only applies to textual facets. If not set, textual values are sorted in natural order; numerical intervals are sorted in the order given by FacetSpec.FacetKey.intervals; FulfillmentInfo.place_ids are sorted in the order given by FacetSpec.FacetKey.restricted_values.
- prefixes List<String>
Only get facet values that start with the given string prefix. For example, suppose "categories" has three values "Women > Shoe", "Women > Dress" and "Men > Shoe". If set "prefixes" to "Women", the "categories" facet will give only "Women > Shoe" and "Women > Dress". Only supported on textual fields. Maximum is 10.
- query String
The query that is used to compute facet for the given facet key. When provided, it will override the default behavior of facet computation. The query syntax is the same as a filter expression. See SearchRequest.filter for detail syntax and limitations. Notice that there is no limitation on FacetKey.key when query is specified. In the response, SearchResponse.Facet.values.value will be always "1" and SearchResponse.Facet.values.count will be the number of results that match the query. For example, you can set a customized facet for "shipToStore", where FacetKey.key is "customizedShipToStore", and FacetKey.query is "availability: ANY("IN_STOCK") AND shipToStore: ANY("123")". Then the facet will count the products that are both in stock and ship to store "123".
- restricted
Values List<String> Only get facet for the given restricted values. For example, when using "pickupInStore" as key and set restricted values to ["store123", "store456"], only facets for "store123" and "store456" are returned. Only supported on predefined textual fields, custom textual attributes and fulfillments. Maximum is 20. Must be set for the fulfillment facet keys: * pickupInStore * shipToStore * sameDayDelivery * nextDayDelivery * customFulfillment1 * customFulfillment2 * customFulfillment3 * customFulfillment4 * customFulfillment5
- return
Min BooleanMax Returns the min and max value for each numerical facet intervals. Ignored for textual facets.
- case
Insensitive boolean True to make facet keys case insensitive when getting faceting values with prefixes or contains; false otherwise.
- contains string[]
Only get facet values that contains the given strings. For example, suppose "categories" has three values "Women > Shoe", "Women > Dress" and "Men > Shoe". If set "contains" to "Shoe", the "categories" facet will give only "Women > Shoe" and "Men > Shoe". Only supported on textual fields. Maximum is 10.
- intervals
Google
Cloud Retail V2beta Interval Response[] For all numerical facet keys that appear in the list of products from the catalog, the percentiles 0, 10, 30, 50, 70, 90 and 100 are computed from their distribution weekly. If the model assigns a high score to a numerical facet key and its intervals are not specified in the search request, these percentiles will become the bounds for its intervals and will be returned in the response. If the facet key intervals are specified in the request, then the specified intervals will be returned instead.
- key string
Supported textual and numerical facet keys in Product object, over which the facet values are computed. Facet key is case-sensitive. Allowed facet keys when FacetKey.query is not specified: * textual_field = * "brands" * "categories" * "genders" * "ageGroups" * "availability" * "colorFamilies" * "colors" * "sizes" * "materials" * "patterns" * "conditions" * "attributes.key" * "pickupInStore" * "shipToStore" * "sameDayDelivery" * "nextDayDelivery" * "customFulfillment1" * "customFulfillment2" * "customFulfillment3" * "customFulfillment4" * "customFulfillment5" * "inventory(place_id,attributes.key)" * numerical_field = * "price" * "discount" * "rating" * "ratingCount" * "attributes.key" * "inventory(place_id,price)" * "inventory(place_id,original_price)" * "inventory(place_id,attributes.key)"
- order
By string The order in which SearchResponse.Facet.values are returned. Allowed values are: * "count desc", which means order by SearchResponse.Facet.values.count descending. * "value desc", which means order by SearchResponse.Facet.values.value descending. Only applies to textual facets. If not set, textual values are sorted in natural order; numerical intervals are sorted in the order given by FacetSpec.FacetKey.intervals; FulfillmentInfo.place_ids are sorted in the order given by FacetSpec.FacetKey.restricted_values.
- prefixes string[]
Only get facet values that start with the given string prefix. For example, suppose "categories" has three values "Women > Shoe", "Women > Dress" and "Men > Shoe". If set "prefixes" to "Women", the "categories" facet will give only "Women > Shoe" and "Women > Dress". Only supported on textual fields. Maximum is 10.
- query string
The query that is used to compute facet for the given facet key. When provided, it will override the default behavior of facet computation. The query syntax is the same as a filter expression. See SearchRequest.filter for detail syntax and limitations. Notice that there is no limitation on FacetKey.key when query is specified. In the response, SearchResponse.Facet.values.value will be always "1" and SearchResponse.Facet.values.count will be the number of results that match the query. For example, you can set a customized facet for "shipToStore", where FacetKey.key is "customizedShipToStore", and FacetKey.query is "availability: ANY("IN_STOCK") AND shipToStore: ANY("123")". Then the facet will count the products that are both in stock and ship to store "123".
- restricted
Values string[] Only get facet for the given restricted values. For example, when using "pickupInStore" as key and set restricted values to ["store123", "store456"], only facets for "store123" and "store456" are returned. Only supported on predefined textual fields, custom textual attributes and fulfillments. Maximum is 20. Must be set for the fulfillment facet keys: * pickupInStore * shipToStore * sameDayDelivery * nextDayDelivery * customFulfillment1 * customFulfillment2 * customFulfillment3 * customFulfillment4 * customFulfillment5
- return
Min booleanMax Returns the min and max value for each numerical facet intervals. Ignored for textual facets.
- case_
insensitive bool True to make facet keys case insensitive when getting faceting values with prefixes or contains; false otherwise.
- contains Sequence[str]
Only get facet values that contains the given strings. For example, suppose "categories" has three values "Women > Shoe", "Women > Dress" and "Men > Shoe". If set "contains" to "Shoe", the "categories" facet will give only "Women > Shoe" and "Men > Shoe". Only supported on textual fields. Maximum is 10.
- intervals
Sequence[Google
Cloud Retail V2beta Interval Response] For all numerical facet keys that appear in the list of products from the catalog, the percentiles 0, 10, 30, 50, 70, 90 and 100 are computed from their distribution weekly. If the model assigns a high score to a numerical facet key and its intervals are not specified in the search request, these percentiles will become the bounds for its intervals and will be returned in the response. If the facet key intervals are specified in the request, then the specified intervals will be returned instead.
- key str
Supported textual and numerical facet keys in Product object, over which the facet values are computed. Facet key is case-sensitive. Allowed facet keys when FacetKey.query is not specified: * textual_field = * "brands" * "categories" * "genders" * "ageGroups" * "availability" * "colorFamilies" * "colors" * "sizes" * "materials" * "patterns" * "conditions" * "attributes.key" * "pickupInStore" * "shipToStore" * "sameDayDelivery" * "nextDayDelivery" * "customFulfillment1" * "customFulfillment2" * "customFulfillment3" * "customFulfillment4" * "customFulfillment5" * "inventory(place_id,attributes.key)" * numerical_field = * "price" * "discount" * "rating" * "ratingCount" * "attributes.key" * "inventory(place_id,price)" * "inventory(place_id,original_price)" * "inventory(place_id,attributes.key)"
- order_
by str The order in which SearchResponse.Facet.values are returned. Allowed values are: * "count desc", which means order by SearchResponse.Facet.values.count descending. * "value desc", which means order by SearchResponse.Facet.values.value descending. Only applies to textual facets. If not set, textual values are sorted in natural order; numerical intervals are sorted in the order given by FacetSpec.FacetKey.intervals; FulfillmentInfo.place_ids are sorted in the order given by FacetSpec.FacetKey.restricted_values.
- prefixes Sequence[str]
Only get facet values that start with the given string prefix. For example, suppose "categories" has three values "Women > Shoe", "Women > Dress" and "Men > Shoe". If set "prefixes" to "Women", the "categories" facet will give only "Women > Shoe" and "Women > Dress". Only supported on textual fields. Maximum is 10.
- query str
The query that is used to compute facet for the given facet key. When provided, it will override the default behavior of facet computation. The query syntax is the same as a filter expression. See SearchRequest.filter for detail syntax and limitations. Notice that there is no limitation on FacetKey.key when query is specified. In the response, SearchResponse.Facet.values.value will be always "1" and SearchResponse.Facet.values.count will be the number of results that match the query. For example, you can set a customized facet for "shipToStore", where FacetKey.key is "customizedShipToStore", and FacetKey.query is "availability: ANY("IN_STOCK") AND shipToStore: ANY("123")". Then the facet will count the products that are both in stock and ship to store "123".
- restricted_
values Sequence[str] Only get facet for the given restricted values. For example, when using "pickupInStore" as key and set restricted values to ["store123", "store456"], only facets for "store123" and "store456" are returned. Only supported on predefined textual fields, custom textual attributes and fulfillments. Maximum is 20. Must be set for the fulfillment facet keys: * pickupInStore * shipToStore * sameDayDelivery * nextDayDelivery * customFulfillment1 * customFulfillment2 * customFulfillment3 * customFulfillment4 * customFulfillment5
- return_
min_ boolmax Returns the min and max value for each numerical facet intervals. Ignored for textual facets.
- case
Insensitive Boolean True to make facet keys case insensitive when getting faceting values with prefixes or contains; false otherwise.
- contains List<String>
Only get facet values that contains the given strings. For example, suppose "categories" has three values "Women > Shoe", "Women > Dress" and "Men > Shoe". If set "contains" to "Shoe", the "categories" facet will give only "Women > Shoe" and "Men > Shoe". Only supported on textual fields. Maximum is 10.
- intervals List<Property Map>
For all numerical facet keys that appear in the list of products from the catalog, the percentiles 0, 10, 30, 50, 70, 90 and 100 are computed from their distribution weekly. If the model assigns a high score to a numerical facet key and its intervals are not specified in the search request, these percentiles will become the bounds for its intervals and will be returned in the response. If the facet key intervals are specified in the request, then the specified intervals will be returned instead.
- key String
Supported textual and numerical facet keys in Product object, over which the facet values are computed. Facet key is case-sensitive. Allowed facet keys when FacetKey.query is not specified: * textual_field = * "brands" * "categories" * "genders" * "ageGroups" * "availability" * "colorFamilies" * "colors" * "sizes" * "materials" * "patterns" * "conditions" * "attributes.key" * "pickupInStore" * "shipToStore" * "sameDayDelivery" * "nextDayDelivery" * "customFulfillment1" * "customFulfillment2" * "customFulfillment3" * "customFulfillment4" * "customFulfillment5" * "inventory(place_id,attributes.key)" * numerical_field = * "price" * "discount" * "rating" * "ratingCount" * "attributes.key" * "inventory(place_id,price)" * "inventory(place_id,original_price)" * "inventory(place_id,attributes.key)"
- order
By String The order in which SearchResponse.Facet.values are returned. Allowed values are: * "count desc", which means order by SearchResponse.Facet.values.count descending. * "value desc", which means order by SearchResponse.Facet.values.value descending. Only applies to textual facets. If not set, textual values are sorted in natural order; numerical intervals are sorted in the order given by FacetSpec.FacetKey.intervals; FulfillmentInfo.place_ids are sorted in the order given by FacetSpec.FacetKey.restricted_values.
- prefixes List<String>
Only get facet values that start with the given string prefix. For example, suppose "categories" has three values "Women > Shoe", "Women > Dress" and "Men > Shoe". If set "prefixes" to "Women", the "categories" facet will give only "Women > Shoe" and "Women > Dress". Only supported on textual fields. Maximum is 10.
- query String
The query that is used to compute facet for the given facet key. When provided, it will override the default behavior of facet computation. The query syntax is the same as a filter expression. See SearchRequest.filter for detail syntax and limitations. Notice that there is no limitation on FacetKey.key when query is specified. In the response, SearchResponse.Facet.values.value will be always "1" and SearchResponse.Facet.values.count will be the number of results that match the query. For example, you can set a customized facet for "shipToStore", where FacetKey.key is "customizedShipToStore", and FacetKey.query is "availability: ANY("IN_STOCK") AND shipToStore: ANY("123")". Then the facet will count the products that are both in stock and ship to store "123".
- restricted
Values List<String> Only get facet for the given restricted values. For example, when using "pickupInStore" as key and set restricted values to ["store123", "store456"], only facets for "store123" and "store456" are returned. Only supported on predefined textual fields, custom textual attributes and fulfillments. Maximum is 20. Must be set for the fulfillment facet keys: * pickupInStore * shipToStore * sameDayDelivery * nextDayDelivery * customFulfillment1 * customFulfillment2 * customFulfillment3 * customFulfillment4 * customFulfillment5
- return
Min BooleanMax Returns the min and max value for each numerical facet intervals. Ignored for textual facets.
GoogleCloudRetailV2betaSearchRequestFacetSpecResponse
- Enable
Dynamic boolPosition Enables dynamic position for this facet. If set to true, the position of this facet among all facets in the response is determined by Google Retail Search. It will be ordered together with dynamic facets if dynamic facets is enabled. If set to false, the position of this facet in the response will be the same as in the request, and it will be ranked before the facets with dynamic position enable and all dynamic facets. For example, you may always want to have rating facet returned in the response, but it's not necessarily to always display the rating facet at the top. In that case, you can set enable_dynamic_position to true so that the position of rating facet in response will be determined by Google Retail Search. Another example, assuming you have the following facets in the request: * "rating", enable_dynamic_position = true * "price", enable_dynamic_position = false * "brands", enable_dynamic_position = false And also you have a dynamic facets enable, which will generate a facet 'gender'. Then the final order of the facets in the response can be ("price", "brands", "rating", "gender") or ("price", "brands", "gender", "rating") depends on how Google Retail Search orders "gender" and "rating" facets. However, notice that "price" and "brands" will always be ranked at 1st and 2nd position since their enable_dynamic_position are false.
- Excluded
Filter List<string>Keys List of keys to exclude when faceting. By default, FacetKey.key is not excluded from the filter unless it is listed in this field. Listing a facet key in this field allows its values to appear as facet results, even when they are filtered out of search results. Using this field does not affect what search results are returned. For example, suppose there are 100 products with the color facet "Red" and 200 products with the color facet "Blue". A query containing the filter "colorFamilies:ANY("Red")" and having "colorFamilies" as FacetKey.key would by default return only "Red" products in the search results, and also return "Red" with count 100 as the only color facet. Although there are also blue products available, "Blue" would not be shown as an available facet value. If "colorFamilies" is listed in "excludedFilterKeys", then the query returns the facet values "Red" with count 100 and "Blue" with count 200, because the "colorFamilies" key is now excluded from the filter. Because this field doesn't affect search results, the search results are still correctly filtered to return only "Red" products. A maximum of 100 values are allowed. Otherwise, an INVALID_ARGUMENT error is returned.
- Facet
Key Pulumi.Google Native. Retail. V2Beta. Inputs. Google Cloud Retail V2beta Search Request Facet Spec Facet Key Response The facet key specification.
- Limit int
Maximum of facet values that should be returned for this facet. If unspecified, defaults to 50. The maximum allowed value is 300. Values above 300 will be coerced to 300. If this field is negative, an INVALID_ARGUMENT is returned.
- Enable
Dynamic boolPosition Enables dynamic position for this facet. If set to true, the position of this facet among all facets in the response is determined by Google Retail Search. It will be ordered together with dynamic facets if dynamic facets is enabled. If set to false, the position of this facet in the response will be the same as in the request, and it will be ranked before the facets with dynamic position enable and all dynamic facets. For example, you may always want to have rating facet returned in the response, but it's not necessarily to always display the rating facet at the top. In that case, you can set enable_dynamic_position to true so that the position of rating facet in response will be determined by Google Retail Search. Another example, assuming you have the following facets in the request: * "rating", enable_dynamic_position = true * "price", enable_dynamic_position = false * "brands", enable_dynamic_position = false And also you have a dynamic facets enable, which will generate a facet 'gender'. Then the final order of the facets in the response can be ("price", "brands", "rating", "gender") or ("price", "brands", "gender", "rating") depends on how Google Retail Search orders "gender" and "rating" facets. However, notice that "price" and "brands" will always be ranked at 1st and 2nd position since their enable_dynamic_position are false.
- Excluded
Filter []stringKeys List of keys to exclude when faceting. By default, FacetKey.key is not excluded from the filter unless it is listed in this field. Listing a facet key in this field allows its values to appear as facet results, even when they are filtered out of search results. Using this field does not affect what search results are returned. For example, suppose there are 100 products with the color facet "Red" and 200 products with the color facet "Blue". A query containing the filter "colorFamilies:ANY("Red")" and having "colorFamilies" as FacetKey.key would by default return only "Red" products in the search results, and also return "Red" with count 100 as the only color facet. Although there are also blue products available, "Blue" would not be shown as an available facet value. If "colorFamilies" is listed in "excludedFilterKeys", then the query returns the facet values "Red" with count 100 and "Blue" with count 200, because the "colorFamilies" key is now excluded from the filter. Because this field doesn't affect search results, the search results are still correctly filtered to return only "Red" products. A maximum of 100 values are allowed. Otherwise, an INVALID_ARGUMENT error is returned.
- Facet
Key GoogleCloud Retail V2beta Search Request Facet Spec Facet Key Response The facet key specification.
- Limit int
Maximum of facet values that should be returned for this facet. If unspecified, defaults to 50. The maximum allowed value is 300. Values above 300 will be coerced to 300. If this field is negative, an INVALID_ARGUMENT is returned.
- enable
Dynamic BooleanPosition Enables dynamic position for this facet. If set to true, the position of this facet among all facets in the response is determined by Google Retail Search. It will be ordered together with dynamic facets if dynamic facets is enabled. If set to false, the position of this facet in the response will be the same as in the request, and it will be ranked before the facets with dynamic position enable and all dynamic facets. For example, you may always want to have rating facet returned in the response, but it's not necessarily to always display the rating facet at the top. In that case, you can set enable_dynamic_position to true so that the position of rating facet in response will be determined by Google Retail Search. Another example, assuming you have the following facets in the request: * "rating", enable_dynamic_position = true * "price", enable_dynamic_position = false * "brands", enable_dynamic_position = false And also you have a dynamic facets enable, which will generate a facet 'gender'. Then the final order of the facets in the response can be ("price", "brands", "rating", "gender") or ("price", "brands", "gender", "rating") depends on how Google Retail Search orders "gender" and "rating" facets. However, notice that "price" and "brands" will always be ranked at 1st and 2nd position since their enable_dynamic_position are false.
- excluded
Filter List<String>Keys List of keys to exclude when faceting. By default, FacetKey.key is not excluded from the filter unless it is listed in this field. Listing a facet key in this field allows its values to appear as facet results, even when they are filtered out of search results. Using this field does not affect what search results are returned. For example, suppose there are 100 products with the color facet "Red" and 200 products with the color facet "Blue". A query containing the filter "colorFamilies:ANY("Red")" and having "colorFamilies" as FacetKey.key would by default return only "Red" products in the search results, and also return "Red" with count 100 as the only color facet. Although there are also blue products available, "Blue" would not be shown as an available facet value. If "colorFamilies" is listed in "excludedFilterKeys", then the query returns the facet values "Red" with count 100 and "Blue" with count 200, because the "colorFamilies" key is now excluded from the filter. Because this field doesn't affect search results, the search results are still correctly filtered to return only "Red" products. A maximum of 100 values are allowed. Otherwise, an INVALID_ARGUMENT error is returned.
- facet
Key GoogleCloud Retail V2beta Search Request Facet Spec Facet Key Response The facet key specification.
- limit Integer
Maximum of facet values that should be returned for this facet. If unspecified, defaults to 50. The maximum allowed value is 300. Values above 300 will be coerced to 300. If this field is negative, an INVALID_ARGUMENT is returned.
- enable
Dynamic booleanPosition Enables dynamic position for this facet. If set to true, the position of this facet among all facets in the response is determined by Google Retail Search. It will be ordered together with dynamic facets if dynamic facets is enabled. If set to false, the position of this facet in the response will be the same as in the request, and it will be ranked before the facets with dynamic position enable and all dynamic facets. For example, you may always want to have rating facet returned in the response, but it's not necessarily to always display the rating facet at the top. In that case, you can set enable_dynamic_position to true so that the position of rating facet in response will be determined by Google Retail Search. Another example, assuming you have the following facets in the request: * "rating", enable_dynamic_position = true * "price", enable_dynamic_position = false * "brands", enable_dynamic_position = false And also you have a dynamic facets enable, which will generate a facet 'gender'. Then the final order of the facets in the response can be ("price", "brands", "rating", "gender") or ("price", "brands", "gender", "rating") depends on how Google Retail Search orders "gender" and "rating" facets. However, notice that "price" and "brands" will always be ranked at 1st and 2nd position since their enable_dynamic_position are false.
- excluded
Filter string[]Keys List of keys to exclude when faceting. By default, FacetKey.key is not excluded from the filter unless it is listed in this field. Listing a facet key in this field allows its values to appear as facet results, even when they are filtered out of search results. Using this field does not affect what search results are returned. For example, suppose there are 100 products with the color facet "Red" and 200 products with the color facet "Blue". A query containing the filter "colorFamilies:ANY("Red")" and having "colorFamilies" as FacetKey.key would by default return only "Red" products in the search results, and also return "Red" with count 100 as the only color facet. Although there are also blue products available, "Blue" would not be shown as an available facet value. If "colorFamilies" is listed in "excludedFilterKeys", then the query returns the facet values "Red" with count 100 and "Blue" with count 200, because the "colorFamilies" key is now excluded from the filter. Because this field doesn't affect search results, the search results are still correctly filtered to return only "Red" products. A maximum of 100 values are allowed. Otherwise, an INVALID_ARGUMENT error is returned.
- facet
Key GoogleCloud Retail V2beta Search Request Facet Spec Facet Key Response The facet key specification.
- limit number
Maximum of facet values that should be returned for this facet. If unspecified, defaults to 50. The maximum allowed value is 300. Values above 300 will be coerced to 300. If this field is negative, an INVALID_ARGUMENT is returned.
- enable_
dynamic_ boolposition Enables dynamic position for this facet. If set to true, the position of this facet among all facets in the response is determined by Google Retail Search. It will be ordered together with dynamic facets if dynamic facets is enabled. If set to false, the position of this facet in the response will be the same as in the request, and it will be ranked before the facets with dynamic position enable and all dynamic facets. For example, you may always want to have rating facet returned in the response, but it's not necessarily to always display the rating facet at the top. In that case, you can set enable_dynamic_position to true so that the position of rating facet in response will be determined by Google Retail Search. Another example, assuming you have the following facets in the request: * "rating", enable_dynamic_position = true * "price", enable_dynamic_position = false * "brands", enable_dynamic_position = false And also you have a dynamic facets enable, which will generate a facet 'gender'. Then the final order of the facets in the response can be ("price", "brands", "rating", "gender") or ("price", "brands", "gender", "rating") depends on how Google Retail Search orders "gender" and "rating" facets. However, notice that "price" and "brands" will always be ranked at 1st and 2nd position since their enable_dynamic_position are false.
- excluded_
filter_ Sequence[str]keys List of keys to exclude when faceting. By default, FacetKey.key is not excluded from the filter unless it is listed in this field. Listing a facet key in this field allows its values to appear as facet results, even when they are filtered out of search results. Using this field does not affect what search results are returned. For example, suppose there are 100 products with the color facet "Red" and 200 products with the color facet "Blue". A query containing the filter "colorFamilies:ANY("Red")" and having "colorFamilies" as FacetKey.key would by default return only "Red" products in the search results, and also return "Red" with count 100 as the only color facet. Although there are also blue products available, "Blue" would not be shown as an available facet value. If "colorFamilies" is listed in "excludedFilterKeys", then the query returns the facet values "Red" with count 100 and "Blue" with count 200, because the "colorFamilies" key is now excluded from the filter. Because this field doesn't affect search results, the search results are still correctly filtered to return only "Red" products. A maximum of 100 values are allowed. Otherwise, an INVALID_ARGUMENT error is returned.
- facet_
key GoogleCloud Retail V2beta Search Request Facet Spec Facet Key Response The facet key specification.
- limit int
Maximum of facet values that should be returned for this facet. If unspecified, defaults to 50. The maximum allowed value is 300. Values above 300 will be coerced to 300. If this field is negative, an INVALID_ARGUMENT is returned.
- enable
Dynamic BooleanPosition Enables dynamic position for this facet. If set to true, the position of this facet among all facets in the response is determined by Google Retail Search. It will be ordered together with dynamic facets if dynamic facets is enabled. If set to false, the position of this facet in the response will be the same as in the request, and it will be ranked before the facets with dynamic position enable and all dynamic facets. For example, you may always want to have rating facet returned in the response, but it's not necessarily to always display the rating facet at the top. In that case, you can set enable_dynamic_position to true so that the position of rating facet in response will be determined by Google Retail Search. Another example, assuming you have the following facets in the request: * "rating", enable_dynamic_position = true * "price", enable_dynamic_position = false * "brands", enable_dynamic_position = false And also you have a dynamic facets enable, which will generate a facet 'gender'. Then the final order of the facets in the response can be ("price", "brands", "rating", "gender") or ("price", "brands", "gender", "rating") depends on how Google Retail Search orders "gender" and "rating" facets. However, notice that "price" and "brands" will always be ranked at 1st and 2nd position since their enable_dynamic_position are false.
- excluded
Filter List<String>Keys List of keys to exclude when faceting. By default, FacetKey.key is not excluded from the filter unless it is listed in this field. Listing a facet key in this field allows its values to appear as facet results, even when they are filtered out of search results. Using this field does not affect what search results are returned. For example, suppose there are 100 products with the color facet "Red" and 200 products with the color facet "Blue". A query containing the filter "colorFamilies:ANY("Red")" and having "colorFamilies" as FacetKey.key would by default return only "Red" products in the search results, and also return "Red" with count 100 as the only color facet. Although there are also blue products available, "Blue" would not be shown as an available facet value. If "colorFamilies" is listed in "excludedFilterKeys", then the query returns the facet values "Red" with count 100 and "Blue" with count 200, because the "colorFamilies" key is now excluded from the filter. Because this field doesn't affect search results, the search results are still correctly filtered to return only "Red" products. A maximum of 100 values are allowed. Otherwise, an INVALID_ARGUMENT error is returned.
- facet
Key Property Map The facet key specification.
- limit Number
Maximum of facet values that should be returned for this facet. If unspecified, defaults to 50. The maximum allowed value is 300. Values above 300 will be coerced to 300. If this field is negative, an INVALID_ARGUMENT is returned.
Package Details
- Repository
- Google Cloud Native pulumi/pulumi-google-native
- License
- Apache-2.0