wall time, but shouldn’t result in prolonged un- availability: PD will allocate timestamps in the future if its own clock falls behind what’s committed to Raft. To improve throughput, PD nodes reserve a hypothesis. We encourage users to instrument their clock rates and alert on divergence, just in case. 4.2 Future Work We recommended that PingCAP disable auto-retry mechanisms by default, and they did so in 3.0 0.0-rc.2. There are safe ways to do transactional auto-retry, which PingCAP may explore in the future, but this is an easy fix which offers users safety right away. We anticipate that 3.0.0, like 3.0.0-rc

versions, be sure to switch to TiCDC and PITR. • The following features are planned for removal in future versions: • Starting from v8.0.0, TiDB Lightning deprecates the old version of conflict de- tection version of conflict detection will be removed in a future release. 2.2.6 Deprecated features The following features are planned for deprecation in future versions: • TiDB introduces the system variable priority queues are enabled to optimize the ordering of tasks that automatically collect statistics. In future releases, the priority queue will be the only way to order tasks for automatically collecting statistics

is deprecated. Starting from v8.3.0, TiDB Binlog is fully deprecated, with removal planned for a future release. For incremental data replication, use TiCDC instead. For point-in-time recovery (PITR), information, see tidb_analyze_column_options. • The following features are planned for deprecation in future versions: • TiDB introduces the system variable tidb_enable_auto_analyze_priority_ �→ queue, which priority queues are enabled to optimize the ordering of tasks that automatically collect statistics. In future releases, the priority queue will be the only way to order tasks for automatically collecting statistics

versions, be sure to switch to TiCDC and PITR. • The following features are planned for removal in future versions: • Starting from v8.0.0, TiDB Lightning deprecates the old version of conflict de- tection version of conflict detection will be removed in a future release. 2.2.6 Deprecated features The following features are planned for deprecation in future versions: • TiDB introduces the system variable priority queues are enabled to optimize the ordering of tasks that automatically collect statistics. In future releases, the priority queue will be the only way to order tasks for automatically collecting statistics

variable tidb_enable_parallel_hashagg_spill, which controls this feature, will be deprecated in a future release. For more information, see documentation. 2.2.1.2 Reliability • Improve statistics loading scattering algorithm is enabled by default. • The following features are planned for deprecation in future versions: • In v8.0.0, TiDB introduces the tidb_enable_auto_analyze_priority_queue system variable to enable the priority queue to optimize the ordering of automatic statistics collection tasks. In future versions, the priority queue will become the only way to order automatic statistics collection tasks

regard- less of the user input. conflict �→ .max �→ - �→ record �→ - �→ rows will be depre- cated in a future release. 50 Configuration file Configuration parame- ter Change type Description TiDB Light- change. • The TiDB Lightning parameter conflict.max-record-rows is scheduled for depre- cation in a future release and will be subsequently removed. This parameter will be replaced by conflict.threshold, The duplicate-resolution parameter for the old version of conflict de- tection will be removed in a future release. 2.2.4 Improvements • TiDB • Improve the MySQL compatibility of foreign keys displayed

regard- less of the user input. conflict �→ .max �→ - �→ record �→ - �→ rows will be depre- cated in a future release. 47 Configuration file Configuration parame- ter Change type Description TiDB Light- change. • The TiDB Lightning parameter conflict.max-record-rows is scheduled for depre- cation in a future release and will be subsequently removed. This parameter will be replaced by conflict.threshold, The duplicate-resolution parameter for the old version of conflict de- tection will be removed in a future release. 51 2.2.4 Improvements • TiDB • Improve the MySQL compatibility of foreign keys displayed

2. The challenges to storage module on HTAP scenario 3. The improvements in TiDB v6.2 4. TiDB's future architectural evolution direction TiDB Core Architecture A typical user case of HTAP workloads 18GB • Peak write throughput deceases over 30% DataSharing TPCH performance improvement TiDB's future architectural evolution direction TiDB Core Architecture Goal: • Better cost efficiency • Faster

Playground. Note: PingCAP does not provide patch releases for DMR versions. Any bugs will be fixed in future releases. For general purposes, it is recommended to use the latest LTS version. The abbreviations been tested and can be used in production environments, and more functions will be supported in the future releases. For functions not listed by this variable, the corresponding expression indexes are not not use meaning- less names that will cause great distress to yourself or your colleagues in the future. It is recommended that you follow your company or organization’s table naming convention. The CREATE

it means enabled. This variable will be deprecated after the feature is generally available in a future release. For more information, see documentation. • Introduce the priority queue for automatic algo- rithm. This vari- able will be depre- cated when this feature is gen- erally avail- able in a future release. 57 Variable name Change type Description tidb_ �→ enable �→ _ �→ fast �→ _ �→ create The duplicate-resolution parameter for the old version of conflict de- tection will be removed in a future release. • It is planned to redesign the auto-evolution of execution plan bindings in subsequent