Queries the maximum number of parallel scan tasks in a single request. You can call the operation to plan the number of parallel scan tasks when you use a search index to export data in parallel.
Request syntax
message ComputeSplitsRequest {
optional string table_name = 1;
optional SearchIndexSplitsOptions search_index_splits_options = 2;
}
|
Parameter |
Type |
Required |
Description |
|
table_name |
string |
Yes |
The name of the data table. |
|
search_index_splits_options |
Yes |
The configuration information about the search index. |
Response syntax
message ComputeSplitsResponse {
optional bytes session_id = 1;
optional int32 splits_size = 2;
}
|
Parameter |
Type |
Required |
Description |
|
session_id |
bytes |
Yes |
The ID of the current session. The value is encoded in the PlainBuffer format. For more information, see PlainBuffer. You can specify session IDs to ensure that the returned result set is stable. |
|
splits_size |
int32 |
Yes |
The maximum number of parallel scan tasks. |
Use Tablestore SDKs
The following Tablestore SDKs support parallel scan:
Tablestore SDK for Java: Parallel scan
Tablestore SDK for Go: Parallel scan
Tablestore SDK for Python: Parallel scan
Tablestore SDK for Node.js: Parallel scan
Tablestore SDK for .NET: Parallel scan
Tablestore SDK for PHP: Parallel scan