- Resource: Evaluation
- EvaluationSpec
- SearchRequest
- ImageQuery
- DataStoreSpec
- BoostSpec
- ConditionBoostSpec
- BoostControlSpec
- AttributeType
- InterpolationType
- ControlPoint
- FacetSpec
- FacetKey
- Interval
- QueryExpansionSpec
- Condition
- SpellCorrectionSpec
- Mode
- EmbeddingSpec
- EmbeddingVector
- NaturalLanguageQueryUnderstandingSpec
- FilterExtractionCondition
- SearchAsYouTypeSpec
- Condition
- SessionSpec
- RelevanceThreshold
- QuerySetSpec
- QualityMetrics
- TopkMetrics
- State
- Methods
Resource: Evaluation
An evaluation is a single execution (or run) of an evaluation process. It encapsulates the state of the evaluation and the resulting data.
JSON representation |
---|
{ "name": string, "evaluationSpec": { object ( |
Fields | |
---|---|
name |
Identifier. The full resource name of the This field must be a UTF-8 encoded string with a length limit of 1024 characters. |
evaluation |
Required. The specification of the evaluation. |
quality |
Output only. The metrics produced by the evaluation, averaged across all Only populated when the evaluation's state is SUCCEEDED. |
state |
Output only. The state of the evaluation. |
error |
Output only. The error that occurred during evaluation. Only populated when the evaluation's state is FAILED. |
create |
Output only. timestamp the A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
end |
Output only. timestamp the A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
error |
Output only. A sample of errors encountered while processing the request. |
EvaluationSpec
Describes the specification of the evaluation.
JSON representation |
---|
{ "querySetSpec": { object ( |
Fields | |
---|---|
query |
Required. The specification of the query set. |
Union field search_spec . The search specification. search_spec can be only one of the following: |
|
search |
Required. The search request that is used to perform the evaluation. Only the following fields within SearchRequest are supported; if any other fields are provided, an UNSUPPORTED error will be returned: |
SearchRequest
Request message for SearchService.Search
method.
JSON representation |
---|
{ "servingConfig": string, "branch": string, "query": string, "imageQuery": { object ( |
Fields | |
---|---|
serving |
Required. The resource name of the Search serving config, such as |
branch |
The branch resource name, such as Use |
query |
Raw search query. |
image |
Raw image query. |
page |
Maximum number of
If this field is negative, an |
page |
A page token received from a previous When paginating, all other parameters provided to |
offset |
A 0-indexed integer that specifies the current offset (that is, starting result location, amongst the If this field is negative, an |
one |
The maximum number of results to return for OneBox. This applies to each OneBox type individually. Default number is 10. |
data |
Specs defining |
filter |
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 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 |
canonical |
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 |
order |
The order in which documents are returned. Documents can be ordered by a field in an 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 |
user |
Information about the end user. Highly recommended for analytics. |
language |
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. |
region |
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. |
facet |
Facet specifications for faceted search. If empty, no facets are returned. A maximum of 100 values are allowed. Otherwise, an |
boost |
Boost specification to boost certain documents. For more information on boosting, see Boosting |
params |
Additional search parameters. For public website search only, supported values are:
For available codes see Country Codes
|
query |
The query expansion specification that specifies the conditions under which query expansion occurs. |
spell |
The spell correction specification that specifies the mode under which spell correction takes effect. |
user |
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 This should be the same identifier as The field must be a UTF-8 encoded string with a length limit of 128 characters. Otherwise, an |
content |
A specification for configuring the behavior of content search. |
embedding |
Uses the provided embedding to do additional semantic document retrieval. The retrieval is based on the dot product of If |
ranking |
The ranking expression controls the customized ranking on retrieval documents. This overrides
Supported functions:
Function variables:
Example ranking expression: If document has an embedding field doc_embedding, the ranking expression could be |
safe |
Whether to turn on safe search. This is only supported for website search. |
user |
The user labels applied to a resource must meet the following requirements:
See Google Cloud Document for more details. |
natural |
If |
search |
Search as you type configuration. Only supported for the |
session |
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): 1. Call /search API with the auto-session mode (see below). 2. 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): 1. Call /search API with the auto-session mode (see below). 2. 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. Auto-session mode: when 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. |
session |
Session specification. Can be used only when |
relevance |
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. |
personalization |
The specification for personalization. Notice that if both |
ImageQuery
Specifies the image query input.
JSON representation |
---|
{ // Union field |
Fields | |
---|---|
Union field
|
|
image |
Base64 encoded image bytes. Supported image formats: JPEG, PNG, and BMP. |
DataStoreSpec
A struct to define data stores to filter on in a search call and configurations for those data stores. Otherwise, an INVALID_ARGUMENT
error is returned.
JSON representation |
---|
{
"dataStore": string,
"filter": string,
"boostSpec": {
object ( |
Fields | |
---|---|
data |
Required. Full resource name of |
filter |
Optional. Filter specification to filter documents in the data store specified by dataStore field. For more information on filtering, see Filtering |
boost |
Optional. Boost specification to boost certain documents. For more information on boosting, see Boosting |
BoostSpec
Boost specification to boost certain documents.
JSON representation |
---|
{
"conditionBoostSpecs": [
{
object ( |
Fields | |
---|---|
condition |
Condition boost specifications. If a document matches multiple conditions in the specifictions, boost scores from these specifications are all applied and combined in a non-linear way. Maximum number of specifications is 20. |
ConditionBoostSpec
Boost applies to documents which match a condition.
JSON representation |
---|
{
"condition": string,
"boost": number,
"boostControlSpec": {
object ( |
Fields | |
---|---|
condition |
An expression which specifies a boost condition. The syntax and supported fields are the same as a filter expression. See Examples:
|
boost |
Strength of the condition boost, which should be in [-1, 1]. Negative boost means demotion. Default is 0.0. Setting to 1.0 gives the document a big promotion. However, it does not necessarily mean that the boosted document will be the top result at all times, nor that other documents 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 documents. Setting to -1.0 gives the document a big demotion. However, results that are deeply relevant might still be shown. The document 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. Only one of the (condition, boost) combination or the boostControlSpec below are set. If both are set then the global boost is ignored and the more fine-grained boostControlSpec is applied. |
boost |
Complex specification for custom ranking based on customer defined attribute value. |
BoostControlSpec
Specification for custom ranking based on customer specified attribute value. It provides more controls for customized ranking than the simple (condition, boost) combination above.
JSON representation |
---|
{ "fieldName": string, "attributeType": enum ( |
Fields | |
---|---|
field |
The name of the field whose value will be used to determine the boost amount. |
attribute |
The attribute type to be used to determine the boost amount. The attribute value can be derived from the field value of the specified fieldName. In the case of numerical it is straightforward i.e. attributeValue = numerical_field_value. In the case of freshness however, attributeValue = (time.now() - datetime_field_value). |
interpolation |
The interpolation type to be applied to connect the control points listed below. |
control |
The control points used to define the curve. The monotonic function (defined through the interpolationType above) passes through the control points listed here. |
AttributeType
The attribute(or function) for which the custom ranking is to be applied.
Enums | |
---|---|
ATTRIBUTE_TYPE_UNSPECIFIED |
Unspecified AttributeType. |
NUMERICAL |
The value of the numerical field will be used to dynamically update the boost amount. In this case, the attributeValue (the x value) of the control point will be the actual value of the numerical field for which the boostAmount is specified. |
FRESHNESS |
For the freshness use case the attribute value will be the duration between the current time and the date in the datetime field specified. The value must be formatted as an XSD dayTimeDuration value (a restricted subset of an ISO 8601 duration value). The pattern for this is: [nD][T[nH][nM][nS]] . For example, 5D , 3DT12H30M , T24H . |
InterpolationType
The interpolation type to be applied. Default will be linear (Piecewise Linear).
Enums | |
---|---|
INTERPOLATION_TYPE_UNSPECIFIED |
Interpolation type is unspecified. In this case, it defaults to Linear. |
LINEAR |
Piecewise linear interpolation will be applied. |
ControlPoint
The control points used to define the curve. The curve defined through these control points can only be monotonically increasing or decreasing(constant values are acceptable).
JSON representation |
---|
{ "attributeValue": string, "boostAmount": number } |
Fields | |
---|---|
attribute |
Can be one of: 1. The numerical field value. 2. The duration spec for freshness: The value must be formatted as an XSD |
boost |
The value between -1 to 1 by which to boost the score if the attributeValue evaluates to the value specified above. |
FacetSpec
A facet specification to perform faceted search.
JSON representation |
---|
{
"facetKey": {
object ( |
Fields | |
---|---|
facet |
Required. The facet key specification. |
limit |
Maximum facet values that are returned for this facet. If unspecified, defaults to 20. The maximum allowed value is 300. Values above 300 are coerced to 300. For aggregation in healthcare search, when the [FacetKey.key] is "healthcare_aggregation_key", the limit will be overridden to 10,000 internally, regardless of the value set here. If this field is negative, an |
excluded |
List of keys to exclude when faceting. By default, 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 documents with the color facet "Red" and 200 documents with the color facet "Blue". A query containing the filter "color:ANY("Red")" and having "color" as If "color" is listed in "excludedFilterKeys", then the query returns the facet values "Red" with count 100 and "Blue" with count 200, because the "color" 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" documents. A maximum of 100 values are allowed. Otherwise, an |
enable |
Enables dynamic position for this facet. If set to true, the position of this facet among all facets in the response is determined automatically. If dynamic facets are enabled, it is ordered together. If set to false, the position of this facet in the response is the same as in the request, and it is 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 enableDynamicPosition to true so that the position of rating facet in response is determined automatically. Another example, assuming you have the following facets in the request:
And also you have a dynamic facets enabled, which generates a facet |
FacetKey
Specifies how a facet is computed.
JSON representation |
---|
{
"key": string,
"intervals": [
{
object ( |
Fields | |
---|---|
key |
Required. Supported textual and numerical facet keys in |
intervals[] |
Set only if values should be bucketed into intervals. Must be set for facets with numerical values. Must not be set for facet with text values. Maximum number of intervals is 30. |
restricted |
Only get facet for the given restricted values. Only supported on textual fields. For example, suppose "category" has three values "Action > 2022", "Action > 2021" and "Sci-Fi > 2022". If set "restrictedValues" to "Action > 2022", the "category" facet only contains "Action > 2022". Only supported on textual fields. Maximum is 10. |
prefixes[] |
Only get facet values that start with the given string prefix. For example, suppose "category" has three values "Action > 2022", "Action > 2021" and "Sci-Fi > 2022". If set "prefixes" to "Action", the "category" facet only contains "Action > 2022" and "Action > 2021". Only supported on textual fields. Maximum is 10. |
contains[] |
Only get facet values that contain the given strings. For example, suppose "category" has three values "Action > 2022", "Action > 2021" and "Sci-Fi > 2022". If set "contains" to "2022", the "category" facet only contains "Action > 2022" and "Sci-Fi > 2022". Only supported on textual fields. Maximum is 10. |
case |
True to make facet keys case insensitive when getting faceting values with prefixes or contains; false otherwise. |
order |
The order in which documents are returned. Allowed values are:
If not set, textual values are sorted in natural order; numerical intervals are sorted in the order given by |
Interval
A floating point interval.
JSON representation |
---|
{ // Union field |
Fields | |
---|---|
Union field This field must be not larger than max. Otherwise, an |
|
minimum |
Inclusive lower bound. |
exclusive |
Exclusive lower bound. |
Union field This field must be not smaller than min. Otherwise, an |
|
maximum |
Inclusive upper bound. |
exclusive |
Exclusive upper bound. |
QueryExpansionSpec
Specification to determine under which conditions query expansion should occur.
JSON representation |
---|
{
"condition": enum ( |
Fields | |
---|---|
condition |
The condition under which query expansion should occur. Default to |
pin |
Whether to pin unexpanded results. If this field is set to true, unexpanded products are always at the top of the search results, followed by the expanded results. |
Condition
Enum describing under which condition query expansion should occur.
Enums | |
---|---|
CONDITION_UNSPECIFIED |
Unspecified query expansion condition. In this case, server behavior defaults to Condition.DISABLED . |
DISABLED |
Disabled query expansion. Only the exact search query is used, even if SearchResponse.total_size is zero. |
AUTO |
Automatic query expansion built by the Search API. |
SpellCorrectionSpec
The specification for query spell correction.
JSON representation |
---|
{
"mode": enum ( |
Fields | |
---|---|
mode |
The mode under which spell correction replaces the original search query. Defaults to |
Mode
Enum describing under which mode spell correction should occur.
Enums | |
---|---|
MODE_UNSPECIFIED |
Unspecified spell correction mode. In this case, server behavior defaults to Mode.AUTO . |
SUGGESTION_ONLY |
Search API tries to find a spelling suggestion. If a suggestion is found, it is put in the SearchResponse.corrected_query . The spelling suggestion won't be used as the search query. |
AUTO |
Automatic spell correction built by the Search API. Search will be based on the corrected query if found. |
EmbeddingSpec
The specification that uses customized query embedding vector to do semantic document retrieval.
JSON representation |
---|
{
"embeddingVectors": [
{
object ( |
Fields | |
---|---|
embedding |
The embedding vector used for retrieval. Limit to 1. |
EmbeddingVector
Embedding vector.
JSON representation |
---|
{ "fieldPath": string, "vector": [ number ] } |
Fields | |
---|---|
field |
Embedding field path in schema. |
vector[] |
Query embedding vector. |
NaturalLanguageQueryUnderstandingSpec
Specification to enable natural language understanding capabilities for search requests.
JSON representation |
---|
{
"filterExtractionCondition": enum ( |
Fields | |
---|---|
filter |
The condition under which filter extraction should occur. Default to [Condition.DISABLED][]. |
geo |
Field names used for location-based filtering, where geolocation filters are detected in natural language search queries. Only valid when the FilterExtractionCondition is set to If this field is set, it overrides the field names set in |
FilterExtractionCondition
Enum describing under which condition filter extraction should occur.
Enums | |
---|---|
CONDITION_UNSPECIFIED |
Server behavior defaults to [Condition.DISABLED][]. |
DISABLED |
Disables NL filter extraction. |
ENABLED |
Enables NL filter extraction. |
SearchAsYouTypeSpec
Specification for search as you type in search requests.
JSON representation |
---|
{
"condition": enum ( |
Fields | |
---|---|
condition |
The condition under which search as you type should occur. Default to |
Condition
Enum describing under which condition search as you type should occur.
Enums | |
---|---|
CONDITION_UNSPECIFIED |
Server behavior defaults to Condition.DISABLED . |
DISABLED |
Disables Search As You Type. |
ENABLED |
Enables Search As You Type. |
SessionSpec
Session specification.
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.
JSON representation |
---|
{ "queryId": string, "searchResultPersistenceCount": integer } |
Fields | |
---|---|
query |
If set, the search result gets stored to the "turn" specified by this query ID. Example: Let's say the session looks like this: session { name: ".../sessions/xxx" turns { query { text: "What is foo?" queryId: ".../questions/yyy" } answer: "Foo is ..." } turns { query { text: "How about bar then?" queryId: ".../questions/zzz" } } } The user can call /search API with a request like this: session: ".../sessions/xxx" sessionSpec { queryId: ".../questions/zzz" } Then, the API stores the search result, associated with the last turn. The stored search result can be used by a subsequent /answer API call (with the session ID and the query ID specified). Also, it is possible to call /search and /answer in parallel with the same session ID & query ID. |
search |
The number of top search results to persist. The persisted search results can be used for the subsequent /answer api call. This field is simliar to the At most 10 results for documents mode, or 50 for chunks mode. |
RelevanceThreshold
The relevance threshold of the search results. The higher relevance threshold is, the higher relevant results are shown and the less number of results are returned.
Enums | |
---|---|
RELEVANCE_THRESHOLD_UNSPECIFIED |
Default value. In this case, server behavior defaults to Google defined threshold. |
LOWEST |
Lowest relevance threshold. |
LOW |
Low relevance threshold. |
MEDIUM |
Medium relevance threshold. |
HIGH |
High relevance threshold. |
QuerySetSpec
Describes the specification of the query set.
JSON representation |
---|
{ "sampleQuerySet": string } |
Fields | |
---|---|
sample |
Required. The full resource name of the |
QualityMetrics
Describes the metrics produced by the evaluation.
JSON representation |
---|
{ "docRecall": { object ( |
Fields | |
---|---|
doc |
Recall per document, at various top-k cutoff levels. Recall is the fraction of relevant documents retrieved out of all relevant documents. Example (top-5): * For a single |
doc |
Precision per document, at various top-k cutoff levels. Precision is the fraction of retrieved documents that are relevant. Example (top-5): * For a single |
doc |
Normalized discounted cumulative gain (NDCG) per document, at various top-k cutoff levels. NDCG measures the ranking quality, giving higher relevance to top results. Example (top-3): Suppose Retrieved: [D3 (0), D1 (1), D2 (1)] Ideal: [D1 (1), D2 (1), D3 (0)] Calculate NDCG@3 for each |
page |
Recall per page, at various top-k cutoff levels. Recall is the fraction of relevant pages retrieved out of all relevant pages. Example (top-5): * For a single |
page |
Normalized discounted cumulative gain (NDCG) per page, at various top-k cutoff levels. NDCG measures the ranking quality, giving higher relevance to top results. Example (top-3): Suppose Retrieved: [P3 (0), P1 (1), P2 (1)] Ideal: [P1 (1), P2 (1), P3 (0)] Calculate NDCG@3 for |
TopkMetrics
Stores the metric values at specific top-k levels.
JSON representation |
---|
{ "top1": number, "top3": number, "top5": number, "top10": number } |
Fields | |
---|---|
top1 |
The top-1 value. |
top3 |
The top-3 value. |
top5 |
The top-5 value. |
top10 |
The top-10 value. |
State
Describes the state of an evaluation.
Enums | |
---|---|
STATE_UNSPECIFIED |
The evaluation is unspecified. |
PENDING |
The service is preparing to run the evaluation. |
RUNNING |
The evaluation is in progress. |
SUCCEEDED |
The evaluation completed successfully. |
FAILED |
The evaluation failed. |
Methods |
|
---|---|
|
Creates a Evaluation . |
|
Gets a Evaluation . |
|
Gets a list of Evaluation s. |
|
Gets a list of results for a given a Evaluation . |