Data writing | - Up to 64 MB of data can be written to Lindorm at a time.
- Up to 2,000 rows can be written to Lindorm at a time.
- If more than 50 files are stored in a single region, the write latency increases.
Note For more information about how to query the number of files stored in a region, see Overview. - If more than 100 files are stored in a single region, errors may occur.
- If more than 200 files are stored in a single region, data cannot be written to the region until the number of files in the region is less than 200.
|
Data deletion | Up to 2,000 rows can be deleted at a time. |
Data reading | - Up to 2,000 values can be specified for the IN operator in SQL queries.
- Up to 2,000 rows or 16 MB of data can be read at a time.
- You must specify the first primary key column or the first index column when you query data.
Note If you do not specify the first primary key column or the first index column in a query request, the query scans all data in the table. By default, this kind of inefficient query requests may be rejected. If you must perform a query without specifying the first primary key or first index column, see the troubleshooting section of SELECT. - When you use the
ORDER BY clause in SQL queries to sort data, you must specify the LIMIT conditions - When you use the
ORDER BY clause in SQL queries to sort data, the values specified for LIMIT and OFFSET cannot be larger than 10000. - When you use the
DISTINCT clause in SQL queries for data deduplication, the number of values specified for DISTINCT cannot exceed 1,000. Otherwise, errors may occur. - When you use the
GROUP BY clause in SQL queries, the number of groups cannot exceed 1,000 for a single instance. Otherwise, errors may occur.
|