| title | aliases | summary | ||
|---|---|---|---|---|
TiDB 2.1.10 Release Notes |
|
TiDB 2.1.10 was released on May 22, 2019, with various bug fixes and improvements. The release includes fixes for issues related to table schema, read results, generated columns, datetime functions, slow logs, and more. Additionally, improvements were made to TiKV and tools like TiDB Lightning and TiDB Binlog. The TiDB Ansible version 2.1.10 also received updates. |
Release date: May 22, 2019
TiDB version: 2.1.10
TiDB Ansible version: 2.1.10
- Fix the issue that some abnormalities cause incorrect table schema when using
tidb_snapshotto read the history data #10359 - Fix the issue that the
NOTfunction causes wrong read results in some cases #10363 - Fix the wrong behavior of
Generated Columnin theReplaceorInsert on duplicate updatestatement #10385 - Fix a bug of the
BETWEENfunction in theDATE/DATETIMEcomparison #10407 - Fix the issue that a single line of a slow log that is too long causes an error report when using the
SLOW_QUERYtable to query a slow log #10412 - Fix the issue that the result of
DATETIMEplusINTERVALis not the same with that of MySQL in some cases #10416, #10418 - Add the check for the invalid time of February in a leap year #10417
- Execute the internal initialization operation limitation only in the DDL owner to avoid a large number of conflict error reports when initializing the cluster #10426
- Fix the issue that
DESCis incompatible with MySQL when the default value of the output timestamp column isdefault current_timestamp on update current_timestamp#10337 - Fix the issue that an error occurs during the privilege check in the
Updatestatement #10439 - Fix the issue that wrong calculation of
RANGEcauses a wrong result in theCHARcolumn in some cases #10455 - Fix the issue that the data might be overwritten after decreasing
SHARD_ROW_ID_BITS#9868 - Fix the issue that
ORDER BY RAND()does not return random numbers #10064 - Prohibit the
ALTERstatement modifying the precision of decimals #10458 - Fix the compatibility issue of the
TIME_FORMATfunction with MySQL #10474 - Check the parameter validity of
PERIOD_ADD#10430 - Fix the issue that the behavior of the invalid
YEARstring in TiDB is incompatible with that in MySQL #10493 - Support the
ALTER DATABASEsyntax #10503 - Fix the issue that the
SLOW_QUERYmemory engine reports an error when no;exists in the slow query statement #10536 - Fix the issue that the
Add indexoperation in partitioned tables cannot be canceled in some cases #10533 - Fix the issue that the OOM panic cannot be recovered in some cases #10545
- Improve the security of the DDL operation rewriting the table metadata #10547
- Fix the issue that the priority of the leader does not take effect #1533
- Reject transferring the leader in a Region whose configuration has been changed recently to avoid transfer failure #4684
- Add the priority label for Coprocessor metrics #4643
- Fix the possible dirty read issue during transferring the leader #4724
- Fix the issue that
CommitMergecauses the restart failure of TiKV in some cases #4615 - Fix unknown logs #4730
- TiDB Lightning
- Add the retry feature when TiDB Lightning fails to send data to
importer#176
- Add the retry feature when TiDB Lightning fails to send data to
- TiDB Binlog
- Optimize the Pump storage log to facilitate troubleshooting #607
- Update the configuration file of TiDB Lightning and add the
tidb_lightning_ctlscript #d3a4a368