Skip to content
Permalink
Browse files

Revert "Revert "dev, v2.1, v3.0: add TiDB 2.1.14 Release Notes (#1315)…

…" (#1316)" (#1317)

This reverts commit 911e760.
  • Loading branch information...
CaitinChen committed Jul 4, 2019
1 parent 911e760 commit 529c7394510493e0997c3c1d518a61091b12efee
Showing with 182 additions and 0 deletions.
  1. +1 −0 dev/TOC.md
  2. +58 −0 dev/releases/2.1.14.md
  3. +2 −0 dev/releases/rn.md
  4. +1 −0 v2.1/TOC.md
  5. +58 −0 v2.1/releases/2.1.14.md
  6. +1 −0 v2.1/releases/rn.md
  7. +1 −0 v3.0/TOC.md
  8. +58 −0 v3.0/releases/2.1.14.md
  9. +2 −0 v3.0/releases/rn.md
@@ -337,6 +337,7 @@
- [3.0.0-beta.1](releases/3.0.0-beta.1.md)
- [3.0.0-beta](releases/3.0beta.md)
+ v2.1
- [2.1.14](/releases/2.1.14.md)
- [2.1.13](releases/2.1.13.md)
- [2.1.12](releases/2.1.12.md)
- [2.1.11](releases/2.1.11.md)
@@ -0,0 +1,58 @@
---
title: TiDB 2.1.14 Release Notes
category: Releases
---

# TiDB 2.1.14 Release Notes

Release date: July 04, 2019

TiDB version: 2.1.14

TiDB Ansible version: 2.1.14


## TiDB

- Fix wrong query results caused by column pruning in some cases [11019](https://github.com/pingcap/tidb/pull/11019)
- Fix the wrongly displayed information in `db` and `info` columns of `show processlist` [11000](https://github.com/pingcap/tidb/pull/11000)
- Fix the issue that `MAX_EXECUTION_TIME` as a SQL hint and global variable does not work in some cases [10999](https://github.com/pingcap/tidb/pull/10999)
- Support automatically adjust the incremental gap allocated by auto-increment ID based on the load [10997](https://github.com/pingcap/tidb/pull/10997)
- Fix the issue that the `Distsql` memory information of `MemTracker` is not correctly cleaned when a query ends [10971](https://github.com/pingcap/tidb/pull/10971)
- Add the `MEM` column in the `information_schema.processlist` table to describe the memory usage of a query [10896](https://github.com/pingcap/tidb/pull/10896)
- Add the `max_execution_time` global system variable to control the maximum execution time of a query [10940](https://github.com/pingcap/tidb/pull/10940)
- Fix the panic caused by using unsupported aggregate functions [10911](https://github.com/pingcap/tidb/pull/10911)
- Add an automatic rollback feature for the last transaction when the `load data` statement fails [10862](https://github.com/pingcap/tidb/pull/10862)
- Fix the issue that TiDB returns a wrong result in some cases when the `OOMAction` configuration item is set to `Cancel` [#11016](https://github.com/pingcap/tidb/pull/11016)
- Disable the `TRACE` statement to avoid the TiDB panic issue [#11039](https://github.com/pingcap/tidb/pull/11039)
- Add the `mysql.expr_pushdown_blacklist` system table that dynamically enables/disables pushing down specific functions to Coprocessor [#10998](https://github.com/pingcap/tidb/pull/10998)
- Fix the issue that the `ANY_VALUE` function does not work in the `ONLY_FULL_GROUP_BY` mode [#10994](https://github.com/pingcap/tidb/pull/10994)
- Fix the incorrect evaluation caused by not doing a deep copy when evaluating the user variable of the string type [#11043](https://github.com/pingcap/tidb/pull/11043)

## TiKV

- Optimize processing the empty callback when processing the Raftstore message to avoid sending unnecessary message [#4682](https://github.com/tikv/tikv/pull/4682)

## PD

- Adjust the log output level from `Error` to `Warning` when reading an invalid configuration item [#1577](https://github.com/pingcap/pd/pull/1577)

## Tools

TiDB Binlog

- Reparo
- Add the `safe-mode` configuration item, and support importing duplicated data after this item is enabled [#662](https://github.com/pingcap/tidb-binlog/pull/662)
- Pump
- Add the `stop-write-at-available-space` configuration item to limit the available binlog space [#659](https://github.com/pingcap/tidb-binlog/pull/659)
- Fix the issue that Garbage Collector does not work sometimes when the number of LevelDB L0 files is 0 [#648](https://github.com/pingcap/tidb-binlog/pull/648)
- Optimize the algorithm of deleting log files to speed up releasing the space [#648](https://github.com/pingcap/tidb-binlog/pull/648)
- Drainer
- Fix the failure to update `BIT` columns in the downstream [#655](https://github.com/pingcap/tidb-binlog/pull/655)

## TiDB Ansible

- Add the precheck feature for the `ansible` command and its `jmespath` and `jinja2` dependency packages [#807](https://github.com/pingcap/tidb-ansible/pull/807)
- Add the `stop-write-at-available-space` parameter (10 GiB by default) in Pump, and stop writing binlog files in Pump when the available disk space is less than the parameter value [#807](https://github.com/pingcap/tidb-ansible/pull/807)


@@ -6,6 +6,7 @@ category: release
# TiDB Release Notes

## 3.0

- [3.0 GA](/releases/3.0-ga.md)
- [3.0.0-rc.3](/releases/3.0.0-rc.3.md)
- [3.0.0-rc.2](/releases/3.0.0-rc.2.md)
@@ -15,6 +16,7 @@ category: release

## 2.1

- [2.1.14](/releases/2.1.14.md)
- [2.1.13](/releases/2.1.13.md)
- [2.1.12](/releases/2.1.12.md)
- [2.1.11](/releases/2.1.11.md)
@@ -326,6 +326,7 @@
- [3.0.0-beta.1](releases/3.0.0-beta.1.md)
- [3.0.0-beta](releases/3.0beta.md)
+ v2.1
- [2.1.14](/releases/2.1.14.md)
- [2.1.13](releases/2.1.13.md)
- [2.1.12](releases/2.1.12.md)
- [2.1.11](releases/2.1.11.md)
@@ -0,0 +1,58 @@
---
title: TiDB 2.1.14 Release Notes
category: Releases
---

# TiDB 2.1.14 Release Notes

Release date: July 04, 2019

TiDB version: 2.1.14

TiDB Ansible version: 2.1.14


## TiDB

- Fix wrong query results caused by column pruning in some cases [11019](https://github.com/pingcap/tidb/pull/11019)
- Fix the wrongly displayed information in `db` and `info` columns of `show processlist` [11000](https://github.com/pingcap/tidb/pull/11000)
- Fix the issue that `MAX_EXECUTION_TIME` as a SQL hint and global variable does not work in some cases [10999](https://github.com/pingcap/tidb/pull/10999)
- Support automatically adjust the incremental gap allocated by auto-increment ID based on the load [10997](https://github.com/pingcap/tidb/pull/10997)
- Fix the issue that the `Distsql` memory information of `MemTracker` is not correctly cleaned when a query ends [10971](https://github.com/pingcap/tidb/pull/10971)
- Add the `MEM` column in the `information_schema.processlist` table to describe the memory usage of a query [10896](https://github.com/pingcap/tidb/pull/10896)
- Add the `max_execution_time` global system variable to control the maximum execution time of a query [10940](https://github.com/pingcap/tidb/pull/10940)
- Fix the panic caused by using unsupported aggregate functions [10911](https://github.com/pingcap/tidb/pull/10911)
- Add an automatic rollback feature for the last transaction when the `load data` statement fails [10862](https://github.com/pingcap/tidb/pull/10862)
- Fix the issue that TiDB returns a wrong result in some cases when the `OOMAction` configuration item is set to `Cancel` [#11016](https://github.com/pingcap/tidb/pull/11016)
- Disable the `TRACE` statement to avoid the TiDB panic issue [#11039](https://github.com/pingcap/tidb/pull/11039)
- Add the `mysql.expr_pushdown_blacklist` system table that dynamically enables/disables pushing down specific functions to Coprocessor [#10998](https://github.com/pingcap/tidb/pull/10998)
- Fix the issue that the `ANY_VALUE` function does not work in the `ONLY_FULL_GROUP_BY` mode [#10994](https://github.com/pingcap/tidb/pull/10994)
- Fix the incorrect evaluation caused by not doing a deep copy when evaluating the user variable of the string type [#11043](https://github.com/pingcap/tidb/pull/11043)

## TiKV

- Optimize processing the empty callback when processing the Raftstore message to avoid sending unnecessary message [#4682](https://github.com/tikv/tikv/pull/4682)

## PD

- Adjust the log output level from `Error` to `Warning` when reading an invalid configuration item [#1577](https://github.com/pingcap/pd/pull/1577)

## Tools

TiDB Binlog

- Reparo
- Add the `safe-mode` configuration item, and support importing duplicated data after this item is enabled [#662](https://github.com/pingcap/tidb-binlog/pull/662)
- Pump
- Add the `stop-write-at-available-space` configuration item to limit the available binlog space [#659](https://github.com/pingcap/tidb-binlog/pull/659)
- Fix the issue that Garbage Collector does not work sometimes when the number of LevelDB L0 files is 0 [#648](https://github.com/pingcap/tidb-binlog/pull/648)
- Optimize the algorithm of deleting log files to speed up releasing the space [#648](https://github.com/pingcap/tidb-binlog/pull/648)
- Drainer
- Fix the failure to update `BIT` columns in the downstream [#655](https://github.com/pingcap/tidb-binlog/pull/655)

## TiDB Ansible

- Add the precheck feature for the `ansible` command and its `jmespath` and `jinja2` dependency packages [#807](https://github.com/pingcap/tidb-ansible/pull/807)
- Add the `stop-write-at-available-space` parameter (10 GiB by default) in Pump, and stop writing binlog files in Pump when the available disk space is less than the parameter value [#807](https://github.com/pingcap/tidb-ansible/pull/807)


@@ -16,6 +16,7 @@ category: release

## 2.1

- [2.1.14](/releases/2.1.14.md)
- [2.1.13](/releases/2.1.13.md)
- [2.1.12](/releases/2.1.12.md)
- [2.1.11](/releases/2.1.11.md)
@@ -337,6 +337,7 @@
- [3.0.0-beta.1](releases/3.0.0-beta.1.md)
- [3.0.0-beta](releases/3.0beta.md)
+ v2.1
- [2.1.14](/releases/2.1.14.md)
- [2.1.13](releases/2.1.13.md)
- [2.1.12](releases/2.1.12.md)
- [2.1.11](releases/2.1.11.md)
@@ -0,0 +1,58 @@
---
title: TiDB 2.1.14 Release Notes
category: Releases
---

# TiDB 2.1.14 Release Notes

Release date: July 04, 2019

TiDB version: 2.1.14

TiDB Ansible version: 2.1.14


## TiDB

- Fix wrong query results caused by column pruning in some cases [11019](https://github.com/pingcap/tidb/pull/11019)
- Fix the wrongly displayed information in `db` and `info` columns of `show processlist` [11000](https://github.com/pingcap/tidb/pull/11000)
- Fix the issue that `MAX_EXECUTION_TIME` as a SQL hint and global variable does not work in some cases [10999](https://github.com/pingcap/tidb/pull/10999)
- Support automatically adjust the incremental gap allocated by auto-increment ID based on the load [10997](https://github.com/pingcap/tidb/pull/10997)
- Fix the issue that the `Distsql` memory information of `MemTracker` is not correctly cleaned when a query ends [10971](https://github.com/pingcap/tidb/pull/10971)
- Add the `MEM` column in the `information_schema.processlist` table to describe the memory usage of a query [10896](https://github.com/pingcap/tidb/pull/10896)
- Add the `max_execution_time` global system variable to control the maximum execution time of a query [10940](https://github.com/pingcap/tidb/pull/10940)
- Fix the panic caused by using unsupported aggregate functions [10911](https://github.com/pingcap/tidb/pull/10911)
- Add an automatic rollback feature for the last transaction when the `load data` statement fails [10862](https://github.com/pingcap/tidb/pull/10862)
- Fix the issue that TiDB returns a wrong result in some cases when the `OOMAction` configuration item is set to `Cancel` [#11016](https://github.com/pingcap/tidb/pull/11016)
- Disable the `TRACE` statement to avoid the TiDB panic issue [#11039](https://github.com/pingcap/tidb/pull/11039)
- Add the `mysql.expr_pushdown_blacklist` system table that dynamically enables/disables pushing down specific functions to Coprocessor [#10998](https://github.com/pingcap/tidb/pull/10998)
- Fix the issue that the `ANY_VALUE` function does not work in the `ONLY_FULL_GROUP_BY` mode [#10994](https://github.com/pingcap/tidb/pull/10994)
- Fix the incorrect evaluation caused by not doing a deep copy when evaluating the user variable of the string type [#11043](https://github.com/pingcap/tidb/pull/11043)

## TiKV

- Optimize processing the empty callback when processing the Raftstore message to avoid sending unnecessary message [#4682](https://github.com/tikv/tikv/pull/4682)

## PD

- Adjust the log output level from `Error` to `Warning` when reading an invalid configuration item [#1577](https://github.com/pingcap/pd/pull/1577)

## Tools

TiDB Binlog

- Reparo
- Add the `safe-mode` configuration item, and support importing duplicated data after this item is enabled [#662](https://github.com/pingcap/tidb-binlog/pull/662)
- Pump
- Add the `stop-write-at-available-space` configuration item to limit the available binlog space [#659](https://github.com/pingcap/tidb-binlog/pull/659)
- Fix the issue that Garbage Collector does not work sometimes when the number of LevelDB L0 files is 0 [#648](https://github.com/pingcap/tidb-binlog/pull/648)
- Optimize the algorithm of deleting log files to speed up releasing the space [#648](https://github.com/pingcap/tidb-binlog/pull/648)
- Drainer
- Fix the failure to update `BIT` columns in the downstream [#655](https://github.com/pingcap/tidb-binlog/pull/655)

## TiDB Ansible

- Add the precheck feature for the `ansible` command and its `jmespath` and `jinja2` dependency packages [#807](https://github.com/pingcap/tidb-ansible/pull/807)
- Add the `stop-write-at-available-space` parameter (10 GiB by default) in Pump, and stop writing binlog files in Pump when the available disk space is less than the parameter value [#807](https://github.com/pingcap/tidb-ansible/pull/807)


@@ -7,6 +7,7 @@ aliases: ['/docs/releases/rn/']
# TiDB Release Notes

## 3.0

- [3.0 GA](/releases/3.0-ga.md)
- [3.0.0-rc.3](/releases/3.0.0-rc.3.md)
- [3.0.0-rc.2](/releases/3.0.0-rc.2.md)
@@ -16,6 +17,7 @@ aliases: ['/docs/releases/rn/']

## 2.1

- [2.1.14](/releases/2.1.14.md)
- [2.1.13](/releases/2.1.13.md)
- [2.1.12](/releases/2.1.12.md)
- [2.1.11](/releases/2.1.11.md)

0 comments on commit 529c739

Please sign in to comment.
You can’t perform that action at this time.