title | aliases | summary | ||
---|---|---|---|---|
TiDB 2.1.5 Release Notes |
|
TiDB 2.1.5 and TiDB Ansible 2.1.5 are released on February 28, 2019. The release improves stability, SQL optimizer, statistics, and execution engine. Fixes include issues with sorting, data overflow, and SQL query results. New features include system variables, HTTP API, and detailed error messages. PD now has an option to exclude Tombstone stores, and TiKV fixes issues with data import, errors, and panic caused by Region merge. Tools like Lightning and TiDB Binlog also receive updates. |
On February 28, 2019, TiDB 2.1.5 is released. The corresponding TiDB Ansible 2.1.5 is also released. Compared with TiDB 2.1.4, this release has greatly improved the stability, the SQL optimizer, statistics, and the execution engine.
- SQL Optimizer/Executor
- Make
SHOW CREATE TABLE
do not print the column charset information when the charset information of a column is the same with that of a table, to improve the compatibility ofSHOW CREATE TABLE
with MySQL #9306 - Fix the panic or the wrong result of the
Sort
operator in some cases by extractingScalarFunc
fromSort
to aProjection
operator for computing to simplify the computing logic ofSort
#9319 - Remove the sorting field with constant values in the
Sort
operator #9335, #9440 - Fix the data overflow issue when inserting data into an unsigned integer column #9339
- Set
cast_as_binary
toNULL
when the length of the target binary exceedsmax_allowed_packet
#9349 - Optimize the constant folding process of
IF
andIFNULL
#9351 - Optimize the index selection of TiDB using skyline pruning to improve the stability of simple queries #9356
- Support computing the selectivity of the
DNF
expression #9405 - Fix the wrong SQL query result of
!=ANY()
and=ALL()
in some cases #9403 - Fix the panic or the wrong result when the Join Key types of two tables on which the
Merge Join
operation is performed are different #9438 - Fix the issue that the result of the
RAND()
function is not compatible with MySQL #9446 - Refactor the logic of
Semi Join
processingNULL
and the empty result set to get the correct result and improve the compatibility with MySQL #9449
- Make
- Server
- Add the
tidb_constraint_check_in_place
system variable to check the data uniqueness constraint when executing theINSERT
statement #9401 - Fix the issue that the value of the
tidb_force_priority
system variable is different from that set in the configuration file #9347 - Add the
current_db
field in general logs to print the name of the currently used database #9346 - Add an HTTP API of obtaining the table information with the table ID #9408
- Fix the issue that
LOAD DATA
loads incorrect data in some cases #9414 - Fix the issue that it takes a long time to build a connection between the MySQL client and TiDB in some cases #9451
- Add the
- DDL
- Fix some issues when canceling the
DROP COLUMN
operation #9352 - Fix some issues when canceling the
DROP
orADD
partitioned table operation #9376 - Fix the issue that
ADMIN CHECK TABLE
mistakenly reports the data index inconsistency in some cases #9399 - Fix the time zone issue of the
TIMESTAMP
default value #9108
- Fix some issues when canceling the
- Provide the
exclude_tombstone_stores
option in theGetAllStores
interface to remove the Tombstone store from the returned result #1444