Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: AUTO_RANDOM为主键应该如何PRESPLIT表
|
username: vincentLi
[TiDB Usage Environment] Production Environment
[TiDB Version] 6.5.3
In the data migration scenario, many tables in the source database do not have primary keys. Due to TiDB’s requirement for primary keys, developers have added some AUTO_RANDOM type IDs as primary keys to these tables for convenience. Most of them are small tables, but there are also large tables.
The data volume is known. Is there any way to pre-shard the data so that it doesn’t need to be split online after reaching the threshold during migration?
AUTO_RANDOM values contain time, making it difficult to predict RANGE and LIST.
TiDB High Concurrency Write Scenario Best Practices | PingCAP Documentation Center
Question Two