title | aliases | summary | ||
---|---|---|---|---|
TiDB 2.1 RC5 Release Notes |
|
TiDB 2.1 RC5 was released on November 12, 2018, with improvements in stability, SQL optimizer, statistics, and execution engine. Fixes include issues with IndexReader, IndexScan Prepared statement, Union statement, and JSON data conversion. Server improvements include log readability, table data retrieval, and environment variable additions. PD fixes issues related to Region key reading, `regions/check` API, PD restart join, and event loss. TiKV improves error messages, adds panic mark file, downgrades grpcio, and adds an upper limit to the `kv_scan` interface. |
On November 12, 2018, TiDB 2.1 RC5 is released. Compared with TiDB 2.1 RC4, this release has great improvement in stability, SQL optimizer, statistics information, and execution engine.
- SQL Optimizer
- SQL Execution Engine
- Statistics
- Server
- Fix the error occurred when obtaining the table data of
infoschema.profiling
#8096 - Replace the unix socket with the pumps client to write binlogs #8098
- Add the threshold value for the
tidb_slow_log_threshold
environment variable, which dynamically sets the slow log #8094 - Add the original length of a SQL statement truncated while the
tidb_query_log_max_len
environment variable dynamically sets logs #8200 - Add the
tidb_opt_write_row_id
environment variable to control whether to allow writing_tidb_rowid
#8218 - Add an upper bound to the
Scan
command of ticlient, to avoid overbound scan #8081, #8247
- Fix the error occurred when obtaining the table data of
- DDL
- Fix the issue that executing DDL statements in transactions encounters an error in some cases #8056
- Fix the issue that executing
truncate table
in partition tables does not take effect #8103 - Fix the issue that the DDL operation does not roll back correctly after being cancelled in some cases #8057
- Add the
admin show next_row_id
command to return the next available row ID #8268
- Fix the issues related to
pd-ctl
reading the Region key - Fix the issue that the
regions/check
API returns the wrong result #1311 - Fix the issue that PD cannot restart join after a PD join failure #1279
- Fix the issue that
watch leader
might lose events in some cases #1317
- Improve the error message of
WriteConflict
#3750 - Add the panic mark file #3746
- Downgrade grpcio to avoid the segment fault issue caused by the new version of gRPC #3650
- Add an upper limit to the
kv_scan
interface #3749
- Support the TiDB-Binlog cluster, which is not compatible with the older version of binlog #8093, documentation