From 88b5fc252f336957b70fc1218c89d4b24c16bf4f Mon Sep 17 00:00:00 2001 From: CaitinChen Date: Fri, 15 Jun 2018 20:49:26 +0800 Subject: [PATCH 1/2] releases, readme: add the release notes for 2.0.4 --- README.md | 1 + releases/204.md | 37 +++++++++++++++++++++++++++++++++++++ releases/rn.md | 3 ++- 3 files changed, 40 insertions(+), 1 deletion(-) create mode 100644 releases/204.md diff --git a/README.md b/README.md index dc79b5358943c..0e6fdf7fcac5b 100644 --- a/README.md +++ b/README.md @@ -128,6 +128,7 @@ - [Frequently Asked Questions (FAQ)](FAQ.md) - [TiDB Best Practices](https://pingcap.github.io/blog/2017/07/24/tidbbestpractice/) + [Releases](releases/rn.md) + - [2.0.4](releases/204.md) - [2.0.3](releases/203.md) - [2.0.2](releases/202.md) - [2.0.1](releases/201.md) diff --git a/releases/204.md b/releases/204.md new file mode 100644 index 0000000000000..5fd47b0825588 --- /dev/null +++ b/releases/204.md @@ -0,0 +1,37 @@ +--- +title: TiDB 2.0.3 Release Notes +category: Releases +--- + +# TiDB 2.0.3 Release Notes + +On June 1, 2018, TiDB 2.0.3 is released. Compared with TiDB 2.0.2, this release has great improvement in system compatibility and stability. + +## TiDB + +- Support modifying the log level online +- Support the `COM_CHANGE_USER` command +- Support using the `TIME` type parameters under the binary protocol +- Optimize the cost estimation of query conditions with the `BETWEEN` expression +- Do not display the `FOREIGN KEY` information in the result of `SHOW CREATE TABLE` +- Optimize the cost estimation for queries with the `LIMIT` clause +- Fix the issue about the `YEAR` type as the unique index +- Fix the issue about `ON DUPLICATE KEY UPDATE` in conditions without the unique index +- Fix the compatibility issue of the `CEIL` function +- Fix the accuracy issue of the `DIV` calculation in the `DECIMAL` type +- Fix the false alarm of `ADMIN CHECK TABLE` +- Fix the panic issue of `MAX`/`MIN` under specific expression parameters +- Fix the issue that the result of `JOIN` is null in special conditions +- Fix the `IN` expression issue when building and querying Range +- Fix a Range calculation issue when using `Prepare` to query and `Plan Cache` is enabled +- Fix the issue that the Schema information is frequently loaded in abnormal conditions + +## PD + +- Fix the panic issue when collecting hot-cache metrics in specific conditions +- Fix the issue about scheduling of the obsolete Regions + +## TiKV + +- Fix the bug that the learner flag mistakenly reports to PD +- Report an error instead of getting a result if `divisor/dividend` is 0 in `do_div_mod` \ No newline at end of file diff --git a/releases/rn.md b/releases/rn.md index c28992210f2fe..7f69d7cab9ebf 100644 --- a/releases/rn.md +++ b/releases/rn.md @@ -4,7 +4,8 @@ category: release --- # TiDB Release Notes - + + - [2.0.4](204.md) - [2.0.3](203.md) - [2.0.2](202.md) - [2.0.1](201.md) From 957cd80a798dc31304ff37914ad33ead5fcb36c4 Mon Sep 17 00:00:00 2001 From: Caitin <34535727+CaitinChen@users.noreply.github.com> Date: Fri, 15 Jun 2018 20:52:45 +0800 Subject: [PATCH 2/2] Update 2.0.4 --- releases/204.md | 50 ++++++++++++++++++++++++++----------------------- 1 file changed, 27 insertions(+), 23 deletions(-) diff --git a/releases/204.md b/releases/204.md index 5fd47b0825588..6e6ce10b8d4f7 100644 --- a/releases/204.md +++ b/releases/204.md @@ -1,37 +1,41 @@ --- -title: TiDB 2.0.3 Release Notes +title: TiDB 2.0.4 Release Notes category: Releases --- -# TiDB 2.0.3 Release Notes +# TiDB 2.0.4 Release Notes -On June 1, 2018, TiDB 2.0.3 is released. Compared with TiDB 2.0.2, this release has great improvement in system compatibility and stability. +On June 15, 2018, TiDB 2.0.4 is released. Compared with TiDB 2.0.3, this release has great improvement in system compatibility and stability. ## TiDB -- Support modifying the log level online -- Support the `COM_CHANGE_USER` command -- Support using the `TIME` type parameters under the binary protocol -- Optimize the cost estimation of query conditions with the `BETWEEN` expression -- Do not display the `FOREIGN KEY` information in the result of `SHOW CREATE TABLE` -- Optimize the cost estimation for queries with the `LIMIT` clause -- Fix the issue about the `YEAR` type as the unique index -- Fix the issue about `ON DUPLICATE KEY UPDATE` in conditions without the unique index -- Fix the compatibility issue of the `CEIL` function -- Fix the accuracy issue of the `DIV` calculation in the `DECIMAL` type -- Fix the false alarm of `ADMIN CHECK TABLE` -- Fix the panic issue of `MAX`/`MIN` under specific expression parameters -- Fix the issue that the result of `JOIN` is null in special conditions -- Fix the `IN` expression issue when building and querying Range -- Fix a Range calculation issue when using `Prepare` to query and `Plan Cache` is enabled -- Fix the issue that the Schema information is frequently loaded in abnormal conditions +- Support the `ALTER TABLE t DROP COLUMN a CASCADE` syntax +- Support configuring the value of `tidb_snapshot` to TSO +- Refine the display of statement types in monitoring items +- Optimize the accuracy of query cost estimation +- Configure the `backoff max delay` parameter of gRPC +- Support configuring the memory threshold of a single statement in the configuration file +- Refactor the error of Optimizer +- Fix the side effects of the `Cast Decimal` data +- Fix the wrong result issue of the `Merge Join` operator in specific scenarios +- Fix the issue of converting the Null object to String +- Fix the issue of casting the JSON type of data to the JSON type +- Fix the issue that the result order is not consistent with MySQL in the condition of `Union` + `OrderBy` +- Fix the compliance rules issue when the `Union` statement checks the `Limit/OrderBy` clause +- Fix the compatibility issue of the `Union All` result +- Fix a bug in predicate pushdown +- Fix the compatibility issue of the `Union` statement with the `For Update` clause +- Fix the issue that the `concat_ws` function mistakenly truncates the result ## PD -- Fix the panic issue when collecting hot-cache metrics in specific conditions -- Fix the issue about scheduling of the obsolete Regions +- Improve the behavior of the unset scheduling argument `max-pending-peer-count` by changing it to no limit for the maximum number of `PendingPeer`s ## TiKV -- Fix the bug that the learner flag mistakenly reports to PD -- Report an error instead of getting a result if `divisor/dividend` is 0 in `do_div_mod` \ No newline at end of file +- Add the RocksDB `PerfContext` interface for debugging +- Remove the `import-mode` parameter +- Add the `region-properties` command for `tikv-ctl` +- Fix the issue that `reverse-seek` is slow when many RocksDB tombstones exist +- Fix the crash issue caused by `do_sub` +- Make GC record the log when GC encounters many versions of data