Limitations of the wide column model
This topic describes the limitations of the wide column model.
Table limits
Item | Limit | Description |
Data table name | Unique within an instance | The following naming conventions apply to data tables:
|
Reserved read/write throughput of a single table | 0 to 100,000 CU | For higher limits, contact technical support or join our DingTalk group: 36165029092. |
Number of predefined columns | 0 to 32 | A predefined column is a non-primary key column with a defined name and data type. It can be used as an indexed field for a secondary index. For higher limits, contact technical support or join our DingTalk group: 36165029092. |
Column limits
Item | Limit | Description |
Column name | Unique within a table | The following naming conventions apply to columns:
|
Number of primary key columns | 1 to 4 | The first primary key column is the partition key. |
Data types of primary key columns | String, Integer, Binary |
|
Number of attribute columns | Unlimited | Although Tablestore does not limit the number of attribute columns, requests may time out when reading extremely wide rows. To prevent this, specify which columns to read or paginate the results. We recommend using fewer than 10,000 attribute columns per row. |
Data types of attribute columns | String, Integer, Double, Boolean, Binary |
Note These size limits apply to each version of an attribute column individually. The limits do not apply to the cumulative size of multiple versions or the total size of all columns in a row. |
Row limits
Item | Limit | Description |
Number of attribute columns in a row | Unlimited | The number of attribute columns in a single row is not limited. |
Size of data in a row | Unlimited | The total data size of a single row is not limited. |
Operation limits
Item | Limit | Description |
Data size per | 4 MB | This limit applies to the total size of primary keys and attribute columns in a single request. |
Data size per | 4 MB | This limit applies to the total size of primary keys and attribute columns in a single request. |
Number of rows per | 200 | This is the maximum number of rows that can be processed in a single |
Data size per | 4 MB | This limit applies to the total data size of all rows in a single |
Number of rows per | 100 | This is the maximum number of rows that can be retrieved in a single |
Data scanned per | 5,000 rows or 4 MB | The scan stops when either 5,000 rows have been scanned or the data size reaches 4 MB. The primary key of the next row is returned to enable pagination. |
Number of attribute columns per write request | 1,024 | A single |
Number of columns in the | 0 to 128 | Specifies the maximum number of columns to retrieve from a single row in one read request. |
Size of an HTTP request body | 5 MB | This is the maximum size of a request body. |
Number of filters in a read request | 10 | This is the maximum number allowed per read request. |
QPS for table metadata operations | 10 per second | The total QPS for all table metadata operations on an instance cannot exceed 10. For more information, see Data table operations. |
Number of | Unlimited | The number of calls is unlimited but constrained by the frequency limit described below. |
Frequency of | Once every 2 minutes | You can adjust a table's reserved read/write throughput at most once every 2 minutes. |