title | aliases | summary | ||
---|---|---|---|---|
TiDB 2.1 RC3 Release Notes |
|
TiDB 2.1 RC3 was released on September 29, 2018, with improvements in stability, compatibility, SQL optimizer, and execution engine. The release includes fixes and enhancements for SQL optimizer, execution engine, server, compatibility, expressions, DML, DDL, and PD. TiKV also received performance optimizations, new features, and bug fixes. |
On September 29, 2018, TiDB 2.1 RC3 is released. Compared with TiDB 2.1 RC2, this release has great improvement in stability, compatibility, SQL optimizer, and execution engine.
- SQL Optimizer
- Fix the incorrect result issue when a statement contains embedded
LEFT OUTER JOIN
#7689 - Enhance the optimization rule of predicate pushdown on the
JOIN
statement #7645 - Fix the optimization rule of predicate pushdown for the
UnionScan
operator #7695 - Fix the issue that the unique key property of the
Union
operator is not correctly set #7680 - Enhance the optimization rule of constant folding #7696
- Optimize the data source in which the filter is null after propagation to table dual #7756
- Fix the incorrect result issue when a statement contains embedded
- SQL Execution Engine
- Server
- Compatibility
- Expressions
- Support the
init_vecter
argument in theAES_ENCRYPT
/AES_DECRYPT
built-in function #7425 - Fix the issue that the result of
Format
is incorrect in some expressions #7770 - Support the
JSON_LENGTH
built-in function #7739 - Fix the incorrect result issue when casting the unsigned integer type to the decimal type #7792
- Support the
- DML
- Fix the issue that the result of the
INSERT … ON DUPLICATE KEY UPDATE
statement is incorrect while updating the unique key #7675
- Fix the issue that the result of the
- DDL
- Fix the issue that the index value is not converted between time zones when you create a new index on a new column of the timestamp type #7724
- Support appending new values for the enum type #7767
- Support creating an etcd session quickly, which improves the cluster availability after network isolation #7774
- New feature
- Add the API to get the Region list by size in reverse order #1254
- Improvement
- Return more detailed information in the Region API #1252
- Bug fix
- Fix the issue that
adjacent-region-scheduler
might lead to a crash after PD switches the leader #1250
- Fix the issue that
- Performance
- Optimize the concurrency for coprocessor requests #3515
- New features
- Bug fixes