Request message for SearchService.Search
method.
JSON representation |
---|
{ "servingConfig" : string , "branch" : string , "query" : string , "imageQuery" : { object ( |
servingConfig
string
Required. The resource name of the Search serving config, such as projects/*/locations/global/collections/default_collection/engines/*/servingConfigs/default_serving_config
, or projects/*/locations/global/collections/default_collection/dataStores/default_data_store/servingConfigs/default_serving_config
. This field is used to identify the serving configuration name, set of models used to make the search.
branch
string
The branch resource name, such as projects/*/locations/global/collections/default_collection/dataStores/default_data_store/branches/0
.
Use default_branch
as the branch ID or leave this field empty, to search documents under the default branch.
query
string
Raw search query.
imageQuery
object (
ImageQuery
)
Raw image query.
pageSize
integer
Maximum number of Document
s to return. The maximum allowed value depends on the data type. Values above the maximum value are coerced to the maximum value.
- Websites with basic indexing: Default
10
, Maximum25
. - Websites with advanced indexing: Default
25
, Maximum50
. - Other: Default
50
, Maximum100
.
If this field is negative, an INVALID_ARGUMENT
is returned.
pageToken
string
A page token received from a previous SearchService.Search
call. Provide this to retrieve the subsequent page.
When paginating, all other parameters provided to SearchService.Search
must match the call that provided the page token. Otherwise, an INVALID_ARGUMENT
error is returned.
offset
oneBoxPageSize
integer
The maximum number of results to return for OneBox. This applies to each OneBox type individually. Default number is 10.
dataStoreSpecs[]
object (
DataStoreSpec
)
Specifications that define the specific DataStore
s to be searched, along with configurations for those data stores. This is only considered for Engine
s with multiple data stores. For engines with a single data store, the specs directly under SearchRequest
should be used.
filter
string
The filter syntax consists of an expression language for constructing a predicate from one or more fields of the documents being filtered. Filter expression is case-sensitive.
If this field is unrecognizable, an INVALID_ARGUMENT
is returned.
Filtering in Vertex AI Search is done by mapping the LHS filter key to a key property defined in the Vertex AI Search backend -- this mapping is defined by the customer in their schema. For example a media customer might have a field 'name' in their schema. In this case the filter would look like this: filter --> name:'ANY("king kong")'
For more information about filtering including syntax and filter operators, see Filter
canonicalFilter
string
The default filter that is applied when a user performs a search without checking any filters on the search page.
The filter applied to every search request when quality improvement such as query expansion is needed. In the case a query does not have a sufficient amount of results this filter will be used to determine whether or not to enable the query expansion flow. The original filter will still be used for the query expanded search. This field is strongly recommended to achieve high search quality.
For more information about filter syntax, see SearchRequest.filter
.
orderBy
string
The order in which documents are returned. Documents can be ordered by a field in an Document
object. Leave it unset if ordered by relevance. orderBy
expression is case-sensitive.
For more information on ordering the website search results, see Order web search results
. For more information on ordering the healthcare search results, see Order healthcare search results
. If this field is unrecognizable, an INVALID_ARGUMENT
is returned.
userInfo
object (
UserInfo
)
Information about the end user. Highly recommended for analytics and personalization. UserInfo.user_agent
is used to deduce deviceType
for analytics.
languageCode
string
The BCP-47 language code, such as "en-US" or "sr-Latn". For more information, see Standard fields . This field helps to better interpret the query. If a value isn't specified, the query language code is automatically detected, which may not be accurate.
regionCode
string
The Unicode country/region code (CLDR) of a location, such as "US" and "419". For more information, see Standard fields . If set, then results will be boosted based on the regionCode provided.
facetSpecs[]
object (
FacetSpec
)
Facet specifications for faceted search. If empty, no facets are returned.
A maximum of 100 values are allowed. Otherwise, an INVALID_ARGUMENT
error is returned.
boostSpec
object (
BoostSpec
)
Boost specification to boost certain documents. For more information on boosting, see Boosting
params
map (key: string, value: value (
Value
format))
Additional search parameters.
For public website search only, supported values are:
-
user_country_code
: string. Default empty. If set to non-empty, results are restricted or boosted based on the location provided. For example,user_country_code: "au"
For available codes see Country Codes
-
searchType
: double. Default empty. Enables non-webpage searching depending on the value. The only valid non-default value is 1, which enables image searching. For example,searchType: 1
queryExpansionSpec
object (
QueryExpansionSpec
)
The query expansion specification that specifies the conditions under which query expansion occurs.
spellCorrectionSpec
object (
SpellCorrectionSpec
)
The spell correction specification that specifies the mode under which spell correction takes effect.
userPseudoId
string
A unique identifier for tracking visitors. For example, this could be implemented with an HTTP cookie, which should be able to uniquely identify a visitor on a single device. This unique identifier should not change if the visitor logs in or out of the website.
This field should NOT have a fixed value such as unknown_visitor
.
This should be the same identifier as UserEvent.user_pseudo_id
and CompleteQueryRequest.user_pseudo_id
The field must be a UTF-8 encoded string with a length limit of 128 characters. Otherwise, an INVALID_ARGUMENT
error is returned.
useLatestData
boolean
uses the Engine, ServingConfig and Control freshly read from the database.
Note: this skips config cache and introduces dependency on databases, which could significantly increase the API latency. It should only be used for testing, but not serving end users.
contentSearchSpec
object (
ContentSearchSpec
)
A specification for configuring the behavior of content search.
rankingExpression
string
Optional. The ranking expression controls the customized ranking on retrieval documents. This overrides ServingConfig.ranking_expression
. The syntax and supported features depend on the rankingExpressionBackend
value. If rankingExpressionBackend
is not provided, it defaults to RANK_BY_EMBEDDING
.
If rankingExpressionBackend
is not provided or set to RANK_BY_EMBEDDING
, it should be a single function or multiple functions that are joined by "+".
- rankingExpression = function, { " + ", function };
Supported functions:
- double * relevanceScore
- double * dotProduct(embedding_field_path)
Function variables:
-
relevanceScore
: pre-defined keywords, used for measure relevance between query and document. -
embedding_field_path
: the document embedding field used with query embedding vector. -
dotProduct
: embedding function betweenembedding_field_path
and query embedding vector.
Example ranking expression:
If document has an embedding field doc_embedding, the ranking expression could be 0.5 * relevanceScore + 0.3 * dotProduct(doc_embedding)
.
If rankingExpressionBackend
is set to RANK_BY_FORMULA
, the following expression types (and combinations of those chained using + or * operators) are supported:
-
double
-
signal
-
log(signal)
-
exp(signal)
-
rr(signal, double > 0)
-- reciprocal rank transformation with second argument being a denominator constant. -
isNan(signal)
-- returns 0 if signal is NaN, 1 otherwise. -
fillNan(signal1, signal2 | double)
-- if signal1 is NaN, returns signal2 | double, else returns signal1.
Here are a few examples of ranking formulas that use the supported ranking expression types:
-
0.2 * semanticSimilarityScore + 0.8 * log(keywordSimilarityScore)
-- mostly rank by the logarithm ofkeywordSimilarityScore
with slightsemantic_smilarity_score
adjustment. -
0.2 * exp(fillNan(semanticSimilarityScore, 0)) + 0.3 * isNan(keywordSimilarityScore)
-- rank by the exponent ofsemanticSimilarityScore
filling the value with 0 if it's NaN, also add constant 0.3 adjustment to the final score ifsemanticSimilarityScore
is NaN. -
0.2 * rr(semanticSimilarityScore, 16) + 0.8 * rr(keywordSimilarityScore, 16)
-- mostly rank by the reciprocal rank ofkeywordSimilarityScore
with slight adjustment of reciprocal rank ofsemantic_smilarity_score
.
The following signals are supported:
-
semanticSimilarityScore
: semantic similarity adjustment that is calculated using the embeddings generated by a proprietary Google model. This score determines how semantically similar a search query is to a document. -
keywordSimilarityScore
: keyword match adjustment uses the Best Match 25 (BM25) ranking function. This score is calculated using a probabilistic model to estimate the probability that a document is relevant to a given query. -
relevanceScore
: semantic relevance adjustment that uses a proprietary Google model to determine the meaning and intent behind a user's query in context with the content in the documents. -
pctrRank
: predicted conversion rate adjustment as a rank use predicted Click-through rate (pCTR) to gauge the relevance and attractiveness of a search result from a user's perspective. A higher pCTR suggests that the result is more likely to satisfy the user's query and intent, making it a valuable signal for ranking. -
freshnessRank
: freshness adjustment as a rank -
documentAge
: The time in hours elapsed since the document was last updated, a floating-point number (e.g., 0.25 means 15 minutes). -
topicalityRank
: topicality adjustment as a rank. uses proprietary Google model to determine the keyword-based overlap between the query and the document. -
baseRank
: the default rank of the result
rankingExpressionBackend
enum (
RankingExpressionBackend
)
Optional. The backend to use for the ranking expression evaluation.
safeSearch
boolean
Whether to turn on safe search. This is only supported for website search.
userLabels
map (key: string, value: string)
The user labels applied to a resource must meet the following requirements:
- Each resource can have multiple labels, up to a maximum of 64.
- Each label must be a key-value pair.
- Keys have a minimum length of 1 character and a maximum length of 63 characters and cannot be empty. Values can be empty and have a maximum length of 63 characters.
- Keys and values can contain only lowercase letters, numeric characters, underscores, and dashes. All characters must use UTF-8 encoding, and international characters are allowed.
- The key portion of a label must be unique. However, you can use the same key with multiple resources.
- Keys must start with a lowercase letter or international character.
See Google Cloud Document for more details.
naturalLanguageQueryUnderstandingSpec
object (
NaturalLanguageQueryUnderstandingSpec
)
Config for natural language query understanding capabilities, such as extracting structured field filters from the query. Refer to this documentation
for more information. If naturalLanguageQueryUnderstandingSpec
is not specified, no additional natural language query understanding will be done.
searchAsYouTypeSpec
object (
SearchAsYouTypeSpec
)
Search as you type configuration. Only supported for the IndustryVertical.MEDIA
vertical.
customFineTuningSpec
object (
CustomFineTuningSpec
)
Custom fine tuning configs. If set, it has higher priority than the configs set in ServingConfig.custom_fine_tuning_spec
.
displaySpec
object (
DisplaySpec
)
Optional. Config for display feature, like match highlighting on search results.
session
string
The session resource name. Optional.
Session allows users to do multi-turn /search API calls or coordination between /search API calls and /answer API calls.
Example #1 (multi-turn /search API calls): Call /search API with the session ID generated in the first call. Here, the previous search query gets considered in query standing. I.e., if the first query is "How did Alphabet do in 2022?" and the current query is "How about 2023?", the current query will be interpreted as "How did Alphabet do in 2023?".
Example #2 (coordination between /search API calls and /answer API calls): Call /answer API with the session ID generated in the first call. Here, the answer generation happens in the context of the search results from the first search call.
Multi-turn Search feature is currently at private GA stage. Please use v1alpha or v1beta version instead before we launch this feature to public GA. Or ask for allowlisting through Google Support team.
sessionSpec
relevanceThreshold
enum (
RelevanceThreshold
)
The relevance threshold of the search results.
Default to Google defined threshold, leveraging a balance of precision and recall to deliver both highly accurate results and comprehensive coverage of relevant information.
This feature is not supported for healthcare search.
personalizationSpec
object (
PersonalizationSpec
)
The specification for personalization.
Notice that if both ServingConfig.personalization_spec
and SearchRequest.personalization_spec
are set, SearchRequest.personalization_spec
overrides ServingConfig.personalization_spec
.
relevanceScoreSpec
object (
RelevanceScoreSpec
)
Optional. The specification for returning the relevance score.