disabled by default. You have the flexibility to manually enable or disable the Titan engine based on your specific requirements. For more information, see documentation. • Support pushing down the following this binding to generate an execution plan for any SQL statement with the same schema, which saves your effort to create a binding for each database. CREATE GLOBAL BINDING FOR USING SELECT /*+ merge_join(t1 this feature with TiCDC. After pausing data replication and conducting pre-online read-write tests in your down- stream TiDB cluster, this feature allows the cluster to gracefully and quickly roll back to

compatible with the MySQL 5.7 protocol, common features of MySQL, and the MySQL ecosystem. To migrate your applications to TiDB, you do not need to change a single line of code in many cases or only need to is enabled by default. It is suitable for various types of DDLs change scenarios. When you upgrade your existing cluster from versions earlier than v6.5.0 to v6.5.0 or later, TiDB automatically enables affecting the online read and write workloads. For more information, see documentation. • Support saving TiFlash query results using the INSERT INTO SELECT statement (ex- perimental) #37515 @gengliqi 35

isolating workloads by Resource Groups, but it makes no calls on how �→ individual queries affect work inside of each group. TiDB v7.2.0 �→ introduces "runaway queries control" to let you control how TiDB wait for the completion of automatic collection tasks. This feature simplifies database maintenance work and improves query performance. For more information, see documentation. 2.2.1.4 Observability Sup- port Y E N N N N N N N N Selecting TiDB nodes for the Dis- tributed eX- e- cu- tion Frame- work (DXF) tasks Y N N N N N N N N N 74 2.4 MySQL Compatibility TiDB is highly compatible with the

data volumes to improve stability. For more information, see documentation. 2.2.1.3 SQL • Support saving TiFlash query results using the INSERT INTO SELECT statement (GA) #37515 @gengliqi Starting from 1.0 supports automatically paus- ing and resuming DDL tasks. Starting from v7.1.0, you can upgrade your clusters without manually canceling DDL tasks in advance. TiDB will automatically pause any running the upgrade and resume these tasks after the rolling upgrade, making it easier for you to upgrade your TiDB clusters. For more information, see documentation. 2.2.1.5 Observability • Enhance optimizer

Managed, you can enjoy the power of open source, distributed SQL while retaining full control over your environment. The following video introduces key features of TiDB. 2.1.1 Key features • Easy horizontal Modified Changes the default value from OFF to ON. This means that Dis- tributed eXecu- tion Frame- work (DXF) is en- abled by de- fault, which fully utilizes the re- sources of the TiDB cluster and greatly digits 0-9, letters a-zA-Z �→ , under- scores _, and hy- phens -. The Dis- tributed eXecu- tion Frame- work (DXF) deter- mines which TiDB nodes can be sched- uled to exe- cute dis- tributed tasks based on the

the usage �→ scenarios of TiDB partitioned tables and avoids some of the �→ application modification work that might be required for data �→ migration. 0 码力 | 6606 页 | 109.48 MB | 10 月前

3

has been upgraded from 13.0 to 17.0. If you are a TiDB developer, you need to upgrade the version of your LLVM compiler to ensure a smooth build. #7193 @Lloyd-Pottiger 2.2.3 Deprecated features • The following might be pushed down incorrectly #37986 @qw4990 • Fix the issue that SELECT INTO OUTFILE does not work when clustered indexes are used as predicates #42093 @qw4990 • Fix the issue that the query latency with a predicate that is always true #46962 @elsa0520 • Fix the issue that using a view does not work in recursive CTE #49721 @hawkingrei • Fix the issue that TiDB might report an error due to GC when

Managed, you can enjoy the power of open source, distributed SQL while retaining full control over your environment. The following video introduces key features of TiDB. 2.1.1 Key features • Easy horizontal usage �→ scenarios of TiDB partitioned tables, and avoids some of the �→ application modification work required for data migration. 42 your-aws-infrastructure/">AWS EC2 �→ now uses IMDSv2 as the default metadata service. TiDB supports

Modified Changes the default value from OFF to ON. This means that Dis- tributed eXecu- tion Frame- work (DXF) is en- abled by de- fault, which fully utilizes the re- sources of the TiDB cluster and greatly digits 0-9, letters a-zA-Z �→ , under- scores _, and hy- phens -. The Dis- tributed eXecu- tion Frame- work (DXF) deter- mines which TiDB nodes can be sched- uled to exe- cute dis- tributed tasks based on the (tidb_partition_prune_mode='static') #52282 @tangenta • Fix the issue that TTL is deviated by 1 hour in daylight saving time #51675 @lcwangchao • Fix the incorrect calculation and display of the number of connections

when ingesting indexed key-value pairs. You can adjust this system variable based on the workload of your cluster. 2.2.2.2 MySQL compatibility • The KEY partition type supports statements with an empty counter opti- mistic trans- action con- flicts, you can cap- ture the error and retry trans- actions in your appli- cation. 50 Variable name Change type Description tidb_ �→ ddl_ �→ version �→ Renamed Controls encountering optimistic transaction conflicts, you can capture the error and retry transactions in your application, or use the Pessimistic transaction mode instead. • Starting from v8.0.0, TiDB no longer