On June 29, 2018, TiDB 2.1 Beta is released! Compared with TiDB 2.0, this release has great improvement in stability, SQL optimizer, statistics information, and execution engine.
Index Join
to improve the execution performanceFilter
, and extend the index range, to improve the efficiency of some queries by orders of magnitudeIndex Hint
and Join Hint
in the UPDATE
and DELETE
statementsTIDM_SMJ
when no available index existsABS
, CEIL
, FLOOR
, IS TRUE
, and IS FALSE
functionsIF
and IFNULL
functions especially in the constant folding processHash Aggregate
operators and improve the computing performance of Hash Aggregate
by 350% in some scenariosProject
operators and improve the performance by 74% in some scenariosInner
table and Outer
table of Hash Join
concurrently to improve the execution performanceINSERT … ON DUPLICATE KEY UPDATE …
in some scenariosCONCAT_WS
, FLOOR
, CEIL
, and DIV
built-in functionsauto_analyze_ratio
system variable to control the threshold value of automatic Analyze
bit
aggregate function support the ALL
parameterSHOW PRIVILEGES
statementINSERT INTO SELECT
statementPlanCache
tidb_retry_limit
system variable to control the automatic retry times of transactionstidb_disable_txn_auto_retry
system variable to control whether the transaction tries automaticallytime
typeAffected Rows
of the UPDATE
statementinsert ignore on duplicate key update
CreateTable
statementADD INDEX
and improve it greatly in some scenariosAlter table add column
exceeds the limit of the number of table columnsFOREIGN KEY
related information in the result of SHOW CREATE TABLE
select tidb_is_ddl_owner()
statement to facilitate judging whether TiDB is DDL Owner
Year
type in some scenariosAlterTableForce
syntaxAlterTableRenameIndex
syntax with FromKey
and ToKey
admin show ddl jobs
region merge
raft learner
by default to lower the risk of unavailable data caused by machine failure during schedulingmax-replica
from pd-recover
Filter
metricsraft learner
by default in the new version of PD. If the cluster is upgraded from 1.x to 2.1, the machine should be stopped before upgrade or a rolling update should be first applied to TiKV and then PDnightly-2018-06-14
versionRaft PreVote
to avoid leader reelection generated when network recovers after network isolationingest
related information in each layer of RocksDBkey
with too many versions when GC worksstatic metric
to optimize multi-label metric performance (YCSB raw get
is improved by 3%)box
in multiple modules and use patterns to improve the operating performance (YCSB raw get
is improved by 3%)asynchronous log
to improve the performance of writing logsbox
used in the application to improve the performanceWhat’s on this page