Wide Column model

Component

Description

Primary key

A primary key uniquely identifies a row in a data table. A primary key consists of one to four primary key columns.

Partition key

The first primary key column is called the partition key. Tablestore partitions data in a data table based on the partition key values. Rows that share the same partition key value are allocated to the same partition to ensure balanced distribution of data access requests.

Attribute column

All columns except for the primary key columns in a row are called attributed columns. Each attribute column can contain values of different versions. Tablestore does not impose limits on the number of attribute columns that can be contained in each row.

Version

Each value in an attribute column has a unique version number. The version number is a timestamp based on which you can manage the TTL of attribute column values. For more information, see Version number.

Data type

Tablestore supports the following data types: String, Binary, Double, Integer, and Boolean. For more information, see Data types.

TTL

You can specify the TTL for each data table. For example, if you set the TTL to one month for a data table, Tablestore automatically deletes data that is written to the data table one month ago. For more information, see TTL.

Max versions

You can specify the maximum number of versions for the value in each attribute column of a data table. Max versions can be used to control the number of versions for the value in each attribute column. When the actual number of versions in an attribute column exceeds the max versions value, Tablestore asynchronously deletes earlier versions. For more information, see Max versions.

Feature

Description

References

Operations on tables

You can list all data tables in an instance, create a data table, query and update the configurations of a data table, and delete a data table.

Operations on a data table

Basic data operations

You can call the PutRow, GetRow, UpdateRow, and DeleteRow operations to perform operations on a single row or call the BatchWriteRow, BatchGetRow, and GetRange operations to perform operations on multiple rows. You can read and write data in a table by calling an operation to perform operations on a single row or multiple rows in the table.

• Write data

• Read data

• Delete data

Max versions and TTL

You can use the max versions and TTL features to manage the lifecycle of your data to optimize storage efficiency and reduce costs.

Data versions and TTL

Auto-increment primary key column

You can specify a primary key column that is not the partition key as the auto-increment primary key column. If you write data to a table that contains an auto-increment primary key column, you do not need to specify values for the auto-increment primary key column. Tablestore automatically generates values for the auto-increment primary key column. The values generated for the auto-increment primary key column are unique and increase monotonically within a partition.

Configure an auto-increment primary key column

Conditional update

If you use conditional update, data in the table can be updated only when the conditions are met. If the conditions are not met, the update fails.

Conditional updates

Local transaction

You can create a local transaction for data that shares the same partition key value. You can read and write data in the local transaction and then commit or discard the local transaction based on your business requirements.

Local transactions

Atomic counter

Atomic counter allows you to implement an atomic counter on a column, and provides real-time statistic data for online applications such as the number of page views (PVs) on various topics.

Use the atomic counter feature

Filter

Filters sort results on the server side. Only results that meet the filter conditions are returned. This feature effectively reduces the volume of transferred data and shortens the response time.

Configure a filter

Secondary index

You can create one or more index tables for a data table and perform queries by using the primary key columns of the index tables. Secondary indexes are classified into global secondary indexes and local secondary indexes.

• When you use a global secondary index, Tablestore automatically synchronizes data from the indexed columns and primary key columns of the data table to the columns of the index table in asynchronous mode. The synchronization latency can be measured in milliseconds.

• When you use a local secondary index, Tablestore automatically synchronizes data from the indexed columns and primary key columns of the data table to the columns of the index table in synchronous mode. You can immediately query the data from the index table after the data is written to the data table.

• Secondary index

• Methods:

  • Use secondary indexes in the Tablestore console

  • Get started with secondary indexes by using Tablestore SDKs

  • Use secondary indexes in the Tablestore CLI

Search index

Search indexes are used for multi-dimensional data queries and statistical analysis in big data scenarios based on inverted indexes and column stores. Search indexes support various query methods, including query based on non-primary key columns, full-text search, prefix query, fuzzy query, Boolean query, nested query, and geo query. Search indexes also support parallel scan and multiple aggregation operations. You can perform aggregation operations to obtain the maximum and minimum values, count and distinct count of rows, sums, and averages, and group results by specific conditions.

• Search index

• Features

• Getting started

• Index management

• Query methods: Basic query, Boolean query, Full-text search, and KNN vector query

• Aggregation

• Export data

SQL query

The SQL query feature provides a unified access interface for multiple data engines. You can use the SQL query feature to perform complex queries and analytics on data in Tablestore in an efficient manner. You can also use indexes in combination with the SQL query feature to optimize queries.

• SQL query

• Use the Tablestore console

• Use Tablestore SDKs

• Use Java Database Connectivity (JDBC)

  • Use JDBC to access Tablestore by executing SQL statements

  • Use Hibernate to query data by executing SQL statements

  • Use MyBatis to query data by executing SQL statements

• Use the Tablestore driver for Go

Tunnel Service

Tunnel Service provides tunnels that are used to export and consume data in full, incremental, and differential modes. After you create a tunnel, you can use it to consume historical and incremental data of a table.

• Tunnel Service

• Quick start

• Use Tunnel Service by using Tablestore SDKs