- JSON representation
- BoostSpecs
- BoostSpec
- ConditionBoostSpec
- BoostControlSpec
- AttributeType
- InterpolationType
- ControlPoint
- FilterSpecs
Configuration specific to search queries with data stores.
JSON representation |
---|
{ "boostSpecs": [ { object ( |
Fields | |
---|---|
boost |
Optional. Boost specifications for data stores. |
filter |
Optional. Filter specification for data store queries. |
BoostSpecs
Boost specifications for data stores.
JSON representation |
---|
{
"dataStores": [
string
],
"spec": [
{
object ( |
Fields | |
---|---|
data |
Optional. Data Stores where the boosting configuration is applied. The full names of the referenced data stores. Formats: |
spec[] |
Optional. A list of boosting specifications. |
BoostSpec
Boost specification to boost certain documents. A copy of google.cloud.discoveryengine.v1main.BoostSpec, field documentation is available at https://cloud.google.com/generative-ai-app-builder/docs/reference/rest/v1alpha/BoostSpec
JSON representation |
---|
{
"conditionBoostSpecs": [
{
object ( |
Fields | |
---|---|
condition |
Optional. 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 |
Optional. An expression which specifies a boost condition. The syntax and supported fields are the same as a filter expression. Examples:
|
boost |
Optional. 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. |
boost |
Optional. 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 |
Optional. The name of the field whose value will be used to determine the boost amount. |
attribute |
Optional. 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 |
Optional. The interpolation type to be applied to connect the control points listed below. |
control |
Optional. 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]] . E.g. 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 |
Optional. Can be one of: 1. The numerical field value. 2. The duration spec for freshness: The value must be formatted as an XSD |
boost |
Optional. The value between -1 to 1 by which to boost the score if the attributeValue evaluates to the value specified above. |
FilterSpecs
Filter specification for data store queries.
JSON representation |
---|
{ "dataStores": [ string ], "filter": string } |
Fields | |
---|---|
data |
Optional. The data store where the filter configuration is applied. Full resource name of data store, such as projects/{project}/locations/{location}/collections/{collectionId}/ dataStores/{dataStoreId}. |
filter |
Optional. The filter expression to be applied. Expression syntax is documented at https://cloud.google.com/generative-ai-app-builder/docs/filter-search-metadata#filter-expression-syntax |