@maxim_mazurok/gapi.client.discoveryengine-v1beta 0.0.20250604 → 0.0.20250609
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/index.d.ts +13 -13
- package/package.json +1 -1
package/index.d.ts
CHANGED
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
// This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
|
|
10
10
|
// In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
|
|
11
11
|
// Generated from: https://discoveryengine.googleapis.com/$discovery/rest?version=v1beta
|
|
12
|
-
// Revision:
|
|
12
|
+
// Revision: 20250609
|
|
13
13
|
|
|
14
14
|
/// <reference types="gapi.client" />
|
|
15
15
|
|
|
@@ -1425,7 +1425,7 @@ declare namespace gapi.client {
|
|
|
1425
1425
|
top5?: number;
|
|
1426
1426
|
}
|
|
1427
1427
|
interface GoogleCloudDiscoveryengineV1alphaQuery {
|
|
1428
|
-
/** Unique Id for the query. */
|
|
1428
|
+
/** Output only. Unique Id for the query. */
|
|
1429
1429
|
queryId?: string;
|
|
1430
1430
|
/** Plain text. */
|
|
1431
1431
|
text?: string;
|
|
@@ -1569,7 +1569,7 @@ declare namespace gapi.client {
|
|
|
1569
1569
|
query?: string;
|
|
1570
1570
|
/** The query expansion specification that specifies the conditions under which query expansion occurs. */
|
|
1571
1571
|
queryExpansionSpec?: GoogleCloudDiscoveryengineV1alphaSearchRequestQueryExpansionSpec;
|
|
1572
|
-
/** The ranking expression controls the customized ranking on retrieval documents. This overrides ServingConfig.ranking_expression. The syntax and supported features depend on the ranking_expression_backend value. If ranking_expression_backend is not provided, it defaults to
|
|
1572
|
+
/** Optional. The ranking expression controls the customized ranking on retrieval documents. This overrides ServingConfig.ranking_expression. The syntax and supported features depend on the `ranking_expression_backend` value. If `ranking_expression_backend` is not provided, it defaults to `RANK_BY_EMBEDDING`. If ranking_expression_backend is not provided or set to `RANK_BY_EMBEDDING`, it should be a single function or multiple functions that are joined by "+". * ranking_expression = function, { " + ", function }; Supported functions: * double * relevance_score * double * dotProduct(embedding_field_path) Function variables: * `relevance_score`: 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 between `embedding_field_path` and query embedding vector. Example ranking expression: If document has an embedding field doc_embedding, the ranking expression could be `0.5 * relevance_score + 0.3 * dotProduct(doc_embedding)`. If ranking_expression_backend 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. * `is_nan(signal)` -- returns 0 if signal is NaN, 1 otherwise. * `fill_nan(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 * semantic_similarity_score + 0.8 * log(keyword_similarity_score)` -- mostly rank by the logarithm of `keyword_similarity_score` with slight `semantic_smilarity_score` adjustment. - `0.2 * exp(fill_nan(semantic_similarity_score, 0)) + 0.3 * is_nan(keyword_similarity_score)` -- rank by the exponent of `semantic_similarity_score` filling the value with 0 if it's NaN, also add constant 0.3 adjustment to the final score if `semantic_similarity_score` is NaN. - `0.2 * rr(semantic_similarity_score, 16) + 0.8 * rr(keyword_similarity_score, 16)` -- mostly rank by the reciprocal rank of `keyword_similarity_score` with slight adjustment of reciprocal rank of `semantic_smilarity_score`. The following signals are supported: * `semantic_similarity_score`: 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. * `keyword_similarity_score`: 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. * `relevance_score`: 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. * `pctr_rank`: 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. * `freshness_rank`: freshness adjustment as a rank * `base_rank`: the default rank of the result */
|
|
1573
1573
|
rankingExpression?: string;
|
|
1574
1574
|
/** Optional. The backend to use for the ranking expression evaluation. */
|
|
1575
1575
|
rankingExpressionBackend?: string;
|
|
@@ -1591,6 +1591,8 @@ declare namespace gapi.client {
|
|
|
1591
1591
|
sessionSpec?: GoogleCloudDiscoveryengineV1alphaSearchRequestSessionSpec;
|
|
1592
1592
|
/** The spell correction specification that specifies the mode under which spell correction takes effect. */
|
|
1593
1593
|
spellCorrectionSpec?: GoogleCloudDiscoveryengineV1alphaSearchRequestSpellCorrectionSpec;
|
|
1594
|
+
/** 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. */
|
|
1595
|
+
useLatestData?: boolean;
|
|
1594
1596
|
/** Information about the end user. Highly recommended for analytics and personalization. UserInfo.user_agent is used to deduce `device_type` for analytics. */
|
|
1595
1597
|
userInfo?: GoogleCloudDiscoveryengineV1alphaUserInfo;
|
|
1596
1598
|
/** 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](https://cloud.google.com/resource-manager/docs/creating-managing-labels#requirements) for more details. */
|
|
@@ -1807,14 +1809,12 @@ declare namespace gapi.client {
|
|
|
1807
1809
|
userPseudoId?: string;
|
|
1808
1810
|
}
|
|
1809
1811
|
interface GoogleCloudDiscoveryengineV1alphaSessionTurn {
|
|
1810
|
-
/** The resource name of the answer to the user query. Only set if the answer generation (/answer API call) happened in this turn. */
|
|
1812
|
+
/** Optional. The resource name of the answer to the user query. Only set if the answer generation (/answer API call) happened in this turn. */
|
|
1811
1813
|
answer?: string;
|
|
1812
1814
|
/** Output only. In ConversationalSearchService.GetSession API, if GetSessionRequest.include_answer_details is set to true, this field will be populated when getting answer query session. */
|
|
1813
1815
|
detailedAnswer?: GoogleCloudDiscoveryengineV1alphaAnswer;
|
|
1814
|
-
/** The user query. */
|
|
1816
|
+
/** Optional. The user query. May not be set if this turn is merely regenerating an answer to a different turn */
|
|
1815
1817
|
query?: GoogleCloudDiscoveryengineV1alphaQuery;
|
|
1816
|
-
/** Optional. Represents metadata related to the query config, for example LLM model and version used, model parameters (temperature, grounding parameters, etc.). We don't want to import directly the [AnswerGenerationSpec] structure as this will serve a more general purpose and a wider set of customers. This information is used in particular when rendering alternative answers to the same prompt, providing visual information about how each answer was generated. The prefix "google." will be reserved for the key, and 1P services (Answer, Assistant, etc.) should always store their information with "google..". 3P services can use anything not starting with "google." */
|
|
1817
|
-
queryConfigs?: {[P in string]: string};
|
|
1818
1818
|
}
|
|
1819
1819
|
interface GoogleCloudDiscoveryengineV1alphaSetDedicatedCrawlRateMetadata {
|
|
1820
1820
|
/** Operation create time. */
|
|
@@ -3896,6 +3896,8 @@ declare namespace gapi.client {
|
|
|
3896
3896
|
}
|
|
3897
3897
|
interface GoogleCloudDiscoveryengineV1betaPauseEngineRequest {}
|
|
3898
3898
|
interface GoogleCloudDiscoveryengineV1betaPrincipal {
|
|
3899
|
+
/** For 3P application identities which are not present in the customer identity provider. */
|
|
3900
|
+
externalEntityId?: string;
|
|
3899
3901
|
/** Group identifier. For Google Workspace user account, group_id should be the google workspace group email. For non-google identity provider user account, group_id is the mapped group identifier configured during the workforcepool config. */
|
|
3900
3902
|
groupId?: string;
|
|
3901
3903
|
/** User identifier. For Google Workspace user account, user_id should be the google workspace user email. For non-google identity provider user account, user_id is the mapped user identifier configured during the workforcepool config. */
|
|
@@ -4025,7 +4027,7 @@ declare namespace gapi.client {
|
|
|
4025
4027
|
top5?: number;
|
|
4026
4028
|
}
|
|
4027
4029
|
interface GoogleCloudDiscoveryengineV1betaQuery {
|
|
4028
|
-
/** Unique Id for the query. */
|
|
4030
|
+
/** Output only. Unique Id for the query. */
|
|
4029
4031
|
queryId?: string;
|
|
4030
4032
|
/** Plain text. */
|
|
4031
4033
|
text?: string;
|
|
@@ -4263,7 +4265,7 @@ declare namespace gapi.client {
|
|
|
4263
4265
|
query?: string;
|
|
4264
4266
|
/** The query expansion specification that specifies the conditions under which query expansion occurs. */
|
|
4265
4267
|
queryExpansionSpec?: GoogleCloudDiscoveryengineV1betaSearchRequestQueryExpansionSpec;
|
|
4266
|
-
/** The ranking expression controls the customized ranking on retrieval documents. This overrides ServingConfig.ranking_expression. The syntax and supported features depend on the ranking_expression_backend value. If ranking_expression_backend is not provided, it defaults to
|
|
4268
|
+
/** Optional. The ranking expression controls the customized ranking on retrieval documents. This overrides ServingConfig.ranking_expression. The syntax and supported features depend on the `ranking_expression_backend` value. If `ranking_expression_backend` is not provided, it defaults to `RANK_BY_EMBEDDING`. If ranking_expression_backend is not provided or set to `RANK_BY_EMBEDDING`, it should be a single function or multiple functions that are joined by "+". * ranking_expression = function, { " + ", function }; Supported functions: * double * relevance_score * double * dotProduct(embedding_field_path) Function variables: * `relevance_score`: 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 between `embedding_field_path` and query embedding vector. Example ranking expression: If document has an embedding field doc_embedding, the ranking expression could be `0.5 * relevance_score + 0.3 * dotProduct(doc_embedding)`. If ranking_expression_backend 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. * `is_nan(signal)` -- returns 0 if signal is NaN, 1 otherwise. * `fill_nan(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 * semantic_similarity_score + 0.8 * log(keyword_similarity_score)` -- mostly rank by the logarithm of `keyword_similarity_score` with slight `semantic_smilarity_score` adjustment. - `0.2 * exp(fill_nan(semantic_similarity_score, 0)) + 0.3 * is_nan(keyword_similarity_score)` -- rank by the exponent of `semantic_similarity_score` filling the value with 0 if it's NaN, also add constant 0.3 adjustment to the final score if `semantic_similarity_score` is NaN. - `0.2 * rr(semantic_similarity_score, 16) + 0.8 * rr(keyword_similarity_score, 16)` -- mostly rank by the reciprocal rank of `keyword_similarity_score` with slight adjustment of reciprocal rank of `semantic_smilarity_score`. The following signals are supported: * `semantic_similarity_score`: 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. * `keyword_similarity_score`: 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. * `relevance_score`: 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. * `pctr_rank`: 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. * `freshness_rank`: freshness adjustment as a rank * `base_rank`: the default rank of the result */
|
|
4267
4269
|
rankingExpression?: string;
|
|
4268
4270
|
/** Optional. The backend to use for the ranking expression evaluation. */
|
|
4269
4271
|
rankingExpressionBackend?: string;
|
|
@@ -4796,14 +4798,12 @@ declare namespace gapi.client {
|
|
|
4796
4798
|
userPseudoId?: string;
|
|
4797
4799
|
}
|
|
4798
4800
|
interface GoogleCloudDiscoveryengineV1betaSessionTurn {
|
|
4799
|
-
/** The resource name of the answer to the user query. Only set if the answer generation (/answer API call) happened in this turn. */
|
|
4801
|
+
/** Optional. The resource name of the answer to the user query. Only set if the answer generation (/answer API call) happened in this turn. */
|
|
4800
4802
|
answer?: string;
|
|
4801
4803
|
/** Output only. In ConversationalSearchService.GetSession API, if GetSessionRequest.include_answer_details is set to true, this field will be populated when getting answer query session. */
|
|
4802
4804
|
detailedAnswer?: GoogleCloudDiscoveryengineV1betaAnswer;
|
|
4803
|
-
/** The user query. */
|
|
4805
|
+
/** Optional. The user query. May not be set if this turn is merely regenerating an answer to a different turn */
|
|
4804
4806
|
query?: GoogleCloudDiscoveryengineV1betaQuery;
|
|
4805
|
-
/** Optional. Represents metadata related to the query config, for example LLM model and version used, model parameters (temperature, grounding parameters, etc.). We don't want to import directly the [AnswerGenerationSpec] structure as this will serve a more general purpose and a wider set of customers. This information is used in particular when rendering alternative answers to the same prompt, providing visual information about how each answer was generated. The prefix "google." will be reserved for the key, and 1P services (Answer, Assistant, etc.) should always store their information with "google..". 3P services can use anything not starting with "google." */
|
|
4806
|
-
queryConfigs?: {[P in string]: string};
|
|
4807
4807
|
}
|
|
4808
4808
|
interface GoogleCloudDiscoveryengineV1betaSetDedicatedCrawlRateMetadata {
|
|
4809
4809
|
/** Operation create time. */
|