ALIYUN::OTS::SearchIndex is used to create a search index for a table. You can create multiple search indexes for a table.

Syntax

{
  "Type": "ALIYUN::OTS::SearchIndex",
  "Properties": {
    "IndexName": String,
    "InstanceName": String,
    "TableName": String,
    "FieldSchemas": List,
    "IndexSort": Map,
    "IndexSetting": Map
  }
}

Properties

Property Type Required Editable Description Constraint
IndexName String Yes No The name of the search index. None
InstanceName String Yes No The name of the instance to which the table belongs. None
TableName String Yes No The name of the table. None
FieldSchemas List Yes No The structure of the field. None
IndexSort Map No No The presorting settings of the index. By default, data is sorted by primary key. Search indexes that contain NEST fields do not support IndexSort.

For more information, see the IndexSort properties section.

IndexSetting Map No No The index settings. For more information, see the IndexSetting properties section.

IndexSort syntax

"IndexSort": {
  "Sorters": List
}

IndexSort properties

Property Type Required Editable Description Constraint
Sorters List Yes No The presorting method for the index. PrimaryKeySort and FieldSort are supported.

For more information, see the Sorters properties section and Sorting and paging.

Sorters syntax

"Sorters": [
  {
    "FieldSort": Map,
    "PrimaryKeySort": Map,
    "ScoreSort": Map,
    "GeoDistanceSort": Map
  }
]

Sorters properties

Property Type Required Editable Description Constraint
FieldSort Map No No Specifies to sort data by field value. For more information, see the FieldSort properties section.
PrimaryKeySort Map No No Specifies to sort data by primary key. For more information, see the PrimaryKeySort properties section.
ScoreSort Map No No Specifies to sort the query result based on the BM25-based keyword relevance score. ScoreSort is applicable to scenarios such as full-text search. You must set ScoreSort to sort the matched data by keyword relevance score. Otherwise, the matched data is sorted based on the IndexSort field value.

For more information, see the ScoreSort properties section.

GeoDistanceSort Map No No Specifies to sort data by geographic distance. For more information, see the GeoDistanceSort properties section.

FieldSort syntax

"FieldSort": {
  "SortMode": String,
  "SortOrder": String,
  "FieldName": String
}

FieldSort properties

Property Type Required Editable Description Constraint
SortMode String No No The sorting method used when the field has multiple values. None
SortOrder String No No The sorting order Default value: ASC. Valid values:
  • ASC: the ascending order.
  • DESC: the descending order.
FieldName String Yes No The name of the field to be sorted. None

PrimaryKeySort syntax

"PrimaryKeySort": {
  "SortOrder": String
}

PrimaryKeySort properties

Property Type Required Editable Description Constraint
SortOrder String No No The sorting order. Default value: ASC. Valid values:
  • ASC: the ascending order.
  • DESC: the descending order.

ScoreSort syntax

"ScoreSort": {
  "SortOrder": String
}

ScoreSort properties

Property Type Required Editable Description Constraint
SortOrder String No No The sorting order. Default value: ASC. Valid values:
  • ASC: the ascending order.
  • DESC: the descending order.

GeoDistanceSort syntax

"GeoDistanceSort": {
  "Points": List,
  "SortMode": String,
  "SortOrder": String,
  "FieldName": String
}

GeoDistanceSort properties

Property Type Required Editable Description Constraint
Points List Yes No The coordinates of the points that compose the polygon. You can specify a polygon by using multiple coordinates in the following format: latitude,longitude. Valid values of latitude: [-90,+90]. Valid values of longitude: [-180,+180]. Example: 35.8,-45.91.
SortMode String No No The sorting method used when the field has multiple values. None
SortOrder String No No The sorting order. Default value: ASC. Valid values:
  • ASC: the ascending order.
  • DESC: the descending order.
FieldName String Yes No The name of the field to be sorted. None

IndexSetting syntax

"IndexSetting": {
  "RoutingFields": List
}

IndexSetting properties

Property Type Required Editable Description Constraint
RoutingFields List No No The custom routing fields. You can specify some primary key columns as routing fields. Tablestore distributes data that is written to a search index to different partitions based on the specified routing fields. The data that has the same routing field value is distributed to the same data partition.

Response parameters

Fn::GetAtt

IndexName: the name of the search index.

Examples

JSON format 

{
  "ROSTemplateFormatVersion": "2015-09-01",
  "Parameters": {
    "IndexName": {
      "Type": "String",
      "Description": "The index name."
    },
    "InstanceName": {
      "Type": "String",
      "Description": "The name of the OTS instance in which table will locate.",
      "AllowedPattern": "[a-zA-Z][-a-zA-Z0-9]{1,14}[a-zA-Z0-9]"
    },
    "TableName": {
      "Type": "String",
      "Description": "The table name of the OTS instance.",
      "AllowedPattern": "[_a-zA-Z][_a-zA-Z0-9]{0,254}"
    },
    "FieldSchemas": {
      "Type": "Json",
      "Description": "list of field_schema."
    },
    "IndexSort": {
      "Type": "Json",
      "Description": "This parameter specifies how data is sorted. \nBy default, the data is sorted in the same way as the primary key of the table. \nIf the search index contains NESTED fields, data is not sorted by default."
    },
    "IndexSetting": {
      "Type": "Json",
      "Description": "Index settings"
    }
  },
  "Resources": {
    "SearchIndex": {
      "Type": "ALIYUN::OTS::SearchIndex",
      "Properties": {
        "IndexName": {
          "Ref": "IndexName"
        },
        "InstanceName": {
          "Ref": "InstanceName"
        },
        "TableName": {
          "Ref": "TableName"
        },
        "FieldSchemas": {
          "Ref": "FieldSchemas"
        },
        "IndexSort": {
          "Ref": "IndexSort"
        },
        "IndexSetting": {
          "Ref": "IndexSetting"
        }
      }
    }
  },
  "Outputs": {
    "IndexName": {
      "Description": "Index name.",
      "Value": {
        "Fn::GetAtt": [
          "SearchIndex",
          "IndexName"
        ]
      }
    }
  }
}

YAML format 

ROSTemplateFormatVersion: '2015-09-01'
Parameters:
  IndexName:
    Type: String
    Description: The index name.
  InstanceName:
    Type: String
    Description: The name of the OTS instance in which table will locate.
    AllowedPattern: '[a-zA-Z][-a-zA-Z0-9]{1,14}[a-zA-Z0-9]'
  TableName:
    Type: String
    Description: The table name of the OTS instance.
    AllowedPattern: '[_a-zA-Z][_a-zA-Z0-9]{0,254}'
  FieldSchemas:
    Type: Json
    Description: list of field_schema.
  IndexSort:
    Type: Json
    Description: >-
      This parameter specifies how data is sorted. 

      By default, the data is sorted in the same way as the primary key of the
      table. 

      If the search index contains NESTED fields, data is not sorted by default.
  IndexSetting:
    Type: Json
    Description: Index settings
Resources:
  SearchIndex:
    Type: 'ALIYUN::OTS::SearchIndex'
    Properties:
      IndexName:
        Ref: IndexName
      InstanceName:
        Ref: InstanceName
      TableName:
        Ref: TableName
      FieldSchemas:
        Ref: FieldSchemas
      IndexSort:
        Ref: IndexSort
      IndexSetting:
        Ref: IndexSetting
Outputs:
  IndexName:
    Description: Index name.
    Value:
      'Fn::GetAtt':
        - SearchIndex
        - IndexName