Merge remote-tracking branch 'upstream/master' into polymorphic-parts

CHANGELOG.md

@@ -641,4 +641,4 @@
 #### Security Fix
 * Fixed the possibility of reading directories structure in tables with `File` table engine. This fixes [#8536](https://github.com/ClickHouse/ClickHouse/issues/8536). [#8537](https://github.com/ClickHouse/ClickHouse/pull/8537) ([alexey-milovidov](https://github.com/alexey-milovidov))
 
-## [Changelog for 2019](https://github.com/ClickHouse/ClickHouse/blob/master/docs/en/changelog/2019.md)
+## [Changelog for 2019](https://github.com/ClickHouse/ClickHouse/blob/master/docs/en/whats_new/changelog/2019.md)

README.md

@@ -15,6 +15,6 @@ ClickHouse is an open-source column-oriented database management system that all
 
 ## Upcoming Events
 
-* [ClickHouse in Avito (online in Russian)](https://avitotech.timepad.ru/event/1290051/) on April 9, 2020.
+* [ClickHouse Monitoring Round Table (online in English)](https://www.eventbrite.com/e/clickhouse-april-virtual-meetup-tickets-102272923066) on April 15, 2020.
 * [ClickHouse Workshop in Novosibirsk](https://2020.codefest.ru/lecture/1628) on TBD date.
 * [Yandex C++ Open-Source Sprints in Moscow](https://events.yandex.ru/events/otkrytyj-kod-v-yandek-28-03-2020) on TBD date.

docker/packager/README.md

@@ -3,10 +3,10 @@ compilers and build settings. Correctly configured Docker daemon is single depen
 
 Usage:
 
-Build deb package with `gcc-8` in `debug` mode:
+Build deb package with `gcc-9` in `debug` mode:
 ```
 $ mkdir deb/test_output
-$ ./packager --output-dir deb/test_output/ --package-type deb --compiler=gcc-8 --build-type=debug
+$ ./packager --output-dir deb/test_output/ --package-type deb --compiler=gcc-9 --build-type=debug
 $ ls -l deb/test_output
 -rw-r--r-- 1 root root      3730 clickhouse-client_18.14.2+debug_all.deb
 -rw-r--r-- 1 root root  84221888 clickhouse-common-static_18.14.2+debug_amd64.deb
@@ -18,11 +18,11 @@ $ ls -l deb/test_output
 
 ```
 
-Build ClickHouse binary with `clang-6.0` and `address` sanitizer in `relwithdebuginfo`
+Build ClickHouse binary with `clang-9.0` and `address` sanitizer in `relwithdebuginfo`
 mode:
 ```
 $ mkdir $HOME/some_clickhouse
-$ ./packager --output-dir=$HOME/some_clickhouse --package-type binary --compiler=clang-6.0 --sanitizer=address
+$ ./packager --output-dir=$HOME/some_clickhouse --package-type binary --compiler=clang-9.0 --sanitizer=address
 $ ls -l $HOME/some_clickhouse
 -rwxr-xr-x 1 root root 787061952  clickhouse
 lrwxrwxrwx 1 root root        10  clickhouse-benchmark -> clickhouse

docker/packager/freebsd/Vagrantfile

@@ -1,4 +0,0 @@
-Vagrant.configure("2") do |config|
-  config.vm.box = "robot-clickhouse/clickhouse-freebsd"
-  config.vm.synced_folder ".", "/vagrant", disabled: true
-end

docker/packager/packager

@@ -11,48 +11,8 @@ SCRIPT_PATH = os.path.realpath(__file__)
 IMAGE_MAP = {
     "deb": "yandex/clickhouse-deb-builder",
     "binary": "yandex/clickhouse-binary-builder",
-    "freebsd": os.path.join(os.path.dirname(SCRIPT_PATH), "freebsd"),
 }
 
-class Vagrant(object):
-    def __init__(self, path_to_vagrant_file):
-        self.prefix = "VAGRANT_CWD=" + path_to_vagrant_file
-
-    def __enter__(self):
-        subprocess.check_call("{} vagrant up".format(self.prefix), shell=True)
-        self.ssh_path = "/tmp/vagrant-ssh"
-        subprocess.check_call("{} vagrant ssh-config > {}".format(self.prefix, self.ssh_path), shell=True)
-        return self
-
-    def copy_to_image(self, local_path, remote_path):
-        cmd = "scp -F {ssh} -r {lpath} default:{rpath}".format(ssh=self.ssh_path, lpath=local_path, rpath=remote_path)
-        logging.info("Copying to image %s", cmd)
-        subprocess.check_call(
-            cmd,
-            shell=True
-        )
-
-    def copy_from_image(self, remote_path, local_path):
-        cmd = "scp -F {ssh} -r default:{rpath} {lpath}".format(ssh=self.ssh_path, rpath=remote_path, lpath=local_path)
-        logging.info("Copying from image %s", cmd)
-        subprocess.check_call(
-            cmd,
-            shell=True
-        )
-
-    def execute_cmd(self, cmd):
-        cmd = '{} vagrant ssh -c "{}"'.format(self.prefix, cmd)
-        logging.info("Executin cmd %s", cmd)
-        subprocess.check_call(
-            cmd,
-            shell=True
-        )
-
-    def __exit__(self, exc_type, exc_val, exc_tb):
-        logging.info("Destroying image")
-        subprocess.check_call("{} vagrant destroy --force".format(self.prefix), shell=True)
-
-
 def check_image_exists_locally(image_name):
     try:
         output = subprocess.check_output("docker images -q {} 2> /dev/null".format(image_name), shell=True)
@@ -94,15 +54,6 @@ def run_docker_image_with_env(image_name, output, env_variables, ch_root, ccache
 
     subprocess.check_call(cmd, shell=True)
 
-def run_vagrant_box_with_env(image_path, output_dir, ch_root):
-    with Vagrant(image_path) as vagrant:
-        logging.info("Copying folder to vagrant machine")
-        vagrant.copy_to_image(ch_root, "~/ClickHouse")
-        logging.info("Running build")
-        vagrant.execute_cmd("cd ~/ClickHouse && cmake . && ninja")
-        logging.info("Copying binary back")
-        vagrant.copy_from_image("~/ClickHouse/programs/clickhouse", output_dir)
-
 def parse_env_variables(build_type, compiler, sanitizer, package_type, image_type, cache, distcc_hosts, unbundled, split_binary, clang_tidy, version, author, official, alien_pkgs, with_coverage):
     CLANG_PREFIX = "clang"
     DARWIN_SUFFIX = "-darwin"
@@ -210,11 +161,11 @@ if __name__ == "__main__":
     logging.basicConfig(level=logging.INFO, format='%(asctime)s %(message)s')
     parser = argparse.ArgumentParser(description="ClickHouse building script using prebuilt Docker image")
     # 'performance' creates a combined .tgz with server and configs to be used for performance test.
-    parser.add_argument("--package-type", choices=['deb', 'binary', 'performance', 'freebsd'], required=True)
+    parser.add_argument("--package-type", choices=['deb', 'binary', 'performance'], required=True)
     parser.add_argument("--clickhouse-repo-path", default="../../")
     parser.add_argument("--output-dir", required=True)
     parser.add_argument("--build-type", choices=("debug", ""), default="")
-    parser.add_argument("--compiler", choices=("clang-8", "clang-8-darwin", "clang-8-aarch64", "gcc-8", "gcc-9", "clang-9"), default="gcc-8")
+    parser.add_argument("--compiler", choices=("clang-8", "clang-8-darwin", "clang-9-aarch64", "clang-9-freebsd", "gcc-8", "gcc-9", "clang-9"), default="gcc-8")
     parser.add_argument("--sanitizer", choices=("address", "thread", "memory", "undefined", ""), default="")
     parser.add_argument("--unbundled", action="store_true")
     parser.add_argument("--split-binary", action="store_true")
@@ -252,9 +203,5 @@ if __name__ == "__main__":
         args.build_type, args.compiler, args.sanitizer, args.package_type, image_type,
         args.cache, args.distcc_hosts, args.unbundled, args.split_binary, args.clang_tidy,
         args.version, args.author, args.official, args.alien_pkgs, args.with_coverage)
-    if image_type != "freebsd":
-        run_docker_image_with_env(image_name, args.output_dir, env_prepared, ch_root, args.ccache_dir)
-    else:
-        logging.info("Running freebsd build, arguments will be ignored")
-        run_vagrant_box_with_env(image_name, args.output_dir, ch_root)
+    run_docker_image_with_env(image_name, args.output_dir, env_prepared, ch_root, args.ccache_dir)
     logging.info("Output placed into {}".format(args.output_dir))

docs/en/commercial/index.md

@@ -1,6 +1,7 @@
 ---
-toc_title: Commercial
 toc_folder_title: Commercial
 toc_priority: 70
+toc_title: Commercial
 ---
 
+

docs/en/development/architecture.md

@@ -41,7 +41,7 @@ Various functions on columns can be implemented in a generic, non-efficient way
 
 ## Block {#block}
 
-A `Block` is a container that represents a subset (chunk) of a table in memory. It is just a set of triples: `(IColumn, IDataType, column name)`. During query execution, data is processed by `Block`s. If we have a `Block`, we have data (in the `IColumn` object), we have information about its type (in `IDataType`) that tells us how to deal with that column, and we have the column name.  It could be either the original column name from the table or some artificial name assigned for getting temporary results of calculations.
+A `Block` is a container that represents a subset (chunk) of a table in memory. It is just a set of triples: `(IColumn, IDataType, column name)`. During query execution, data is processed by `Block`s. If we have a `Block`, we have data (in the `IColumn` object), we have information about its type (in `IDataType`) that tells us how to deal with that column, and we have the column name. It could be either the original column name from the table or some artificial name assigned for getting temporary results of calculations.
 
 When we calculate some function over columns in a block, we add another column with its result to the block, and we don’t touch columns for arguments of the function because operations are immutable. Later, unneeded columns can be removed from the block, but not modified. It is convenient for the elimination of common subexpressions.
 
@@ -77,7 +77,7 @@ For byte-oriented input/output, there are `ReadBuffer` and `WriteBuffer` abstrac
 
 Implementations of `ReadBuffer`/`WriteBuffer` are used for working with files and file descriptors and network sockets, for implementing compression (`CompressedWriteBuffer` is initialized with another WriteBuffer and performs compression before writing data to it), and for other purposes – the names `ConcatReadBuffer`, `LimitReadBuffer`, and `HashingWriteBuffer` speak for themselves.
 
-Read/WriteBuffers only deal with bytes. There are functions from `ReadHelpers` and `WriteHelpers` header files to help with formatting input/output.  For example, there are helpers to write a number in decimal format.
+Read/WriteBuffers only deal with bytes. There are functions from `ReadHelpers` and `WriteHelpers` header files to help with formatting input/output. For example, there are helpers to write a number in decimal format.
 
 Let’s look at what happens when you want to write a result set in `JSON` format to stdout. You have a result set ready to be fetched from `IBlockInputStream`. You create `WriteBufferFromFileDescriptor(STDOUT_FILENO)` to write bytes to stdout. You create `JSONRowOutputStream`, initialized with that `WriteBuffer`, to write rows in `JSON` to stdout. You create `BlockOutputStreamFromRowOutputStream` on top of it, to represent it as `IBlockOutputStream`. Then you call `copyData` to transfer data from `IBlockInputStream` to `IBlockOutputStream`, and everything works. Internally, `JSONRowOutputStream` will write various JSON delimiters and call the `IDataType::serializeTextJSON` method with a reference to `IColumn` and the row number as arguments. Consequently, `IDataType::serializeTextJSON` will call a method from `WriteHelpers.h`: for example, `writeText` for numeric types and `writeJSONString` for `DataTypeString`.
 
@@ -155,7 +155,7 @@ The server initializes the `Context` class with the necessary environment for qu
 We maintain full backward and forward compatibility for the server TCP protocol: old clients can talk to new servers, and new clients can talk to old servers. But we don’t want to maintain it eternally, and we are removing support for old versions after about one year.
 
 !!! note "Note"
-	For most external applications, we recommend using the HTTP interface because it is simple and easy to use. The TCP protocol is more tightly linked to internal data structures: it uses an internal format for passing blocks of data, and it uses custom framing for compressed data. We haven’t released a C library for that protocol because it requires linking most of the ClickHouse codebase, which is not practical.
+    For most external applications, we recommend using the HTTP interface because it is simple and easy to use. The TCP protocol is more tightly linked to internal data structures: it uses an internal format for passing blocks of data, and it uses custom framing for compressed data. We haven’t released a C library for that protocol because it requires linking most of the ClickHouse codebase, which is not practical.
 
 ## Distributed Query Execution {#distributed-query-execution}
 

docs/en/development/build_cross_arm.md

@@ -3,7 +3,7 @@ toc_priority: 67
 toc_title: How to Build ClickHouse on Linux for AARCH64 (ARM64)
 ---
 
-# How to Build ClickHouse on Linux for AARCH64 (ARM64) architecture {#how-to-build-clickhouse-on-linux-for-aarch64-arm64-architecture}
+# How to Build ClickHouse on Linux for AARCH64 (ARM64) Architecture {#how-to-build-clickhouse-on-linux-for-aarch64-arm64-architecture}
 
 This is for the case when you have Linux machine and want to use it to build `clickhouse` binary that will run on another Linux machine with AARCH64 CPU architecture. This is intended for continuous integration checks that run on Linux servers.
 

docs/en/development/contrib.md

@@ -6,7 +6,7 @@ toc_title: Third-Party Libraries Used
 # Third-Party Libraries Used {#third-party-libraries-used}
 
 | Library             | License                                                                                                                                      |
-|-------------|--------------------------------------------------------------------------------------|
+|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
 | base64              | [BSD 2-Clause License](https://github.com/aklomp/base64/blob/a27c565d1b6c676beaf297fe503c4518185666f7/LICENSE)                               |
 | boost               | [Boost Software License 1.0](https://github.com/ClickHouse-Extras/boost-extra/blob/6883b40449f378019aec792f9983ce3afc7ff16e/LICENSE_1_0.txt) |
 | brotli              | [MIT](https://github.com/google/brotli/blob/master/LICENSE)                                                                                  |

docs/en/development/developer_instruction.md

@@ -5,15 +5,15 @@ toc_title: The Beginner ClickHouse Developer Instruction
 
 Building of ClickHouse is supported on Linux, FreeBSD and Mac OS X.
 
-# If you use Windows {#if-you-use-windows}
+# If You Use Windows {#if-you-use-windows}
 
 If you use Windows, you need to create a virtual machine with Ubuntu. To start working with a virtual machine please install VirtualBox. You can download Ubuntu from the website: https://www.ubuntu.com/\#download. Please create a virtual machine from the downloaded image (you should reserve at least 4GB of RAM for it). To run a command-line terminal in Ubuntu, please locate a program containing the word “terminal” in its name (gnome-terminal, konsole etc.) or just press Ctrl+Alt+T.
 
-# If you use a 32-bit system {#if-you-use-a-32-bit-system}
+# If You Use a 32-bit System {#if-you-use-a-32-bit-system}
 
 ClickHouse cannot work or build on a 32-bit system. You should acquire access to a 64-bit system and you can continue reading.
 
-# Creating a repository on GitHub {#creating-a-repository-on-github}
+# Creating a Repository on GitHub {#creating-a-repository-on-github}
 
 To start working with ClickHouse repository you will need a GitHub account.
 
@@ -33,7 +33,7 @@ To do that in Ubuntu you would run in the command line terminal:
 A brief manual on using Git can be found here: https://services.github.com/on-demand/downloads/github-git-cheat-sheet.pdf.
 For a detailed manual on Git see https://git-scm.com/book/en/v2.
 
-# Cloning a repository to your development machine {#cloning-a-repository-to-your-development-machine}
+# Cloning a Repository to Your Development Machine {#cloning-a-repository-to-your-development-machine}
 
 Next, you need to download the source files onto your working machine. This is called “to clone a repository” because it creates a local copy of the repository on your working machine.
 
@@ -77,7 +77,7 @@ You can also add original ClickHouse repo’s address to your local repository t
 
 After successfully running this command you will be able to pull updates from the main ClickHouse repo by running `git pull upstream master`.
 
-## Working with submodules {#working-with-submodules}
+## Working with Submodules {#working-with-submodules}
 
 Working with submodules in git could be painful. Next commands will help to manage it:
 
@@ -145,7 +145,7 @@ Mac OS X build is supported only for Clang. Just run `brew install llvm`
 
 If you decide to use Clang, you can also install `libc++` and `lld`, if you know what it is. Using `ccache` is also recommended.
 
-# The Building process {#the-building-process}
+# The Building Process {#the-building-process}
 
 Now that you are ready to build ClickHouse we recommend you to create a separate directory `build` inside `ClickHouse` that will contain all of the build artefacts:
 
@@ -202,7 +202,7 @@ Upon successful build you get an executable file `ClickHouse/<build_dir>/program
 
     ls -l programs/clickhouse
 
-# Running the built executable of ClickHouse {#running-the-built-executable-of-clickhouse}
+# Running the Built Executable of ClickHouse {#running-the-built-executable-of-clickhouse}
 
 To run the server under the current user you need to navigate to `ClickHouse/programs/server/` (located outside of `build`) and run:
 

docs/en/development/tests.md

@@ -11,7 +11,7 @@ Functional tests are the most simple and convenient to use. Most of ClickHouse f
 
 Each functional test sends one or multiple queries to the running ClickHouse server and compares the result with reference.
 
-Tests are located in `testsies` directory. There are two subdirectories: `stateless` and `stateful`. Stateless tests run queries without any preloaded test data - they often create small synthetic datasets on the fly, within the test itself. Stateful tests require preloaded test data from Yandex.Metrica and not available to general public. We tend to use only `stateless` tests and avoid adding new `stateful` tests.
+Tests are located in `queries` directory. There are two subdirectories: `stateless` and `stateful`. Stateless tests run queries without any preloaded test data - they often create small synthetic datasets on the fly, within the test itself. Stateful tests require preloaded test data from Yandex.Metrica and not available to general public. We tend to use only `stateless` tests and avoid adding new `stateful` tests.
 
 Each test can be one of two types: `.sql` and `.sh`. `.sql` test is the simple SQL script that is piped to `clickhouse-client --multiquery --testmode`. `.sh` test is a script that is run by itself.
 
@@ -19,7 +19,7 @@ To run all tests, use `testskhouse-test` tool. Look `--help` for the list of pos
 
 The most simple way to invoke functional tests is to copy `clickhouse-client` to `/usr/bin/`, run `clickhouse-server` and then run `./clickhouse-test` from its own directory.
 
-To add new test, create a `.sql` or `.sh` file in `testsies/0_stateless` directory, check it manually and then generate `.reference` file in the following way: `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` or `./00000_test.sh > ./00000_test.reference`.
+To add new test, create a `.sql` or `.sh` file in `queries/0_stateless` directory, check it manually and then generate `.reference` file in the following way: `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` or `./00000_test.sh > ./00000_test.reference`.
 
 Tests should use (create, drop, etc) only tables in `test` database that is assumed to be created beforehand; also tests can use temporary tables.
 
@@ -32,9 +32,9 @@ meaning. `long` is for tests that run slightly longer that one second. You can
 disable these groups of tests using `--no-zookeeper`, `--no-shard` and
 `--no-long` options, respectively.
 
-## Known bugs {#known-bugs}
+## Known Bugs {#known-bugs}
 
-If we know some bugs that can be easily reproduced by functional tests, we place prepared functional tests in `testsies/bugs` directory. These tests will be moved to `teststests_stateless` when bugs are fixed.
+If we know some bugs that can be easily reproduced by functional tests, we place prepared functional tests in `queries/bugs` directory. These tests will be moved to `teststests_stateless` when bugs are fixed.
 
 ## Integration Tests {#integration-tests}
 
@@ -58,7 +58,7 @@ Each test run one or miltiple queries (possibly with combinations of parameters)
 
 If you want to improve performance of ClickHouse in some scenario, and if improvements can be observed on simple queries, it is highly recommended to write a performance test. It always makes sense to use `perf top` or other perf tools during your tests.
 
-## Test Tools And Scripts {#test-tools-and-scripts}
+## Test Tools and Scripts {#test-tools-and-scripts}
 
 Some programs in `tests` directory are not prepared tests, but are test tools. For example, for `Lexer` there is a tool `src/Parsers/tests/lexer` that just do tokenization of stdin and writes colorized result to stdout. You can use these kind of tools as a code examples and for exploration and manual testing.
 
@@ -163,11 +163,11 @@ For example, build with system packages is bad practice, because we cannot guara
 
 Though we cannot run all tests on all variant of builds, we want to check at least that various build variants are not broken. For this purpose we use build tests.
 
-## Testing For Protocol Compatibility {#testing-for-protocol-compatibility}
+## Testing for Protocol Compatibility {#testing-for-protocol-compatibility}
 
 When we extend ClickHouse network protocol, we test manually that old clickhouse-client works with new clickhouse-server and new clickhouse-client works with old clickhouse-server (simply by running binaries from corresponding packages).
 
-## Help From The Compiler {#help-from-the-compiler}
+## Help from the Compiler {#help-from-the-compiler}
 
 Main ClickHouse code (that is located in `dbms` directory) is built with `-Wall -Wextra -Werror` and with some additional enabled warnings. Although these options are not enabled for third-party libraries.
 

docs/en/engines/database_engines/mysql.md

@@ -3,7 +3,7 @@ toc_priority: 30
 toc_title: MySQL
 ---
 
-# Mysql {#mysql}
+# MySQL {#mysql}
 
 Allows to connect to databases on a remote MySQL server and perform `INSERT` and `SELECT` queries to exchange data between ClickHouse and MySQL.
 
@@ -19,7 +19,7 @@ You cannot perform the following queries:
 
 ``` sql
 CREATE DATABASE [IF NOT EXISTS] db_name [ON CLUSTER cluster]
-ENGINE = MySQL('host:port', 'database', 'user', 'password')
+ENGINE = MySQL('host:port', ['database' | database], 'user', 'password')
 ```
 
 **Engine Parameters**

docs/en/engines/index.md

@@ -3,3 +3,4 @@ toc_folder_title: Engines
 toc_priority: 25
 ---
 
+

docs/en/engines/table_engines/index.md

@@ -17,7 +17,7 @@ The table engine (type of table) determines:
 
 ## Engine Families {#engine-families}
 
-### Mergetree {#mergetree}
+### MergeTree {#mergetree}
 
 The most universal and functional table engines for high-load tasks. The property shared by these engines is quick data insertion with subsequent background data processing. `MergeTree` family engines support data replication (with [Replicated\*](mergetree_family/replication.md) versions of engines), partitioning, and other features not supported in other engines.
 

docs/en/engines/table_engines/mergetree_family/collapsingmergetree.md

@@ -3,7 +3,7 @@ toc_priority: 36
 toc_title: CollapsingMergeTree
 ---
 
-# Collapsingmergetree {#table_engine-collapsingmergetree}
+# CollapsingMergeTree {#table_engine-collapsingmergetree}
 
 The engine inherits from [MergeTree](mergetree.md) and adds the logic of rows collapsing to data parts merge algorithm.
 

docs/en/engines/table_engines/mergetree_family/graphitemergetree.md

@@ -3,7 +3,7 @@ toc_priority: 38
 toc_title: GraphiteMergeTree
 ---
 
-# Graphitemergetree {#graphitemergetree}
+# GraphiteMergeTree {#graphitemergetree}
 
 This engine is designed for thinning and aggregating/averaging (rollup) [Graphite](http://graphite.readthedocs.io/en/latest/index.html) data. It may be helpful to developers who want to use ClickHouse as a data store for Graphite.
 

docs/en/engines/table_engines/mergetree_family/mergetree.md

@@ -3,7 +3,7 @@ toc_priority: 30
 toc_title: MergeTree
 ---
 
-# Mergetree {#table_engines-mergetree}
+# MergeTree {#table_engines-mergetree}
 
 The `MergeTree` engine and other engines of this family (`*MergeTree`) are the most robust ClickHouse table engines.
 

docs/en/engines/table_engines/mergetree_family/replacingmergetree.md

@@ -3,7 +3,7 @@ toc_priority: 33
 toc_title: ReplacingMergeTree
 ---
 
-# Replacingmergetree {#replacingmergetree}
+# ReplacingMergeTree {#replacingmergetree}
 
 The engine differs from [MergeTree](mergetree.md#table_engines-mergetree) in that it removes duplicate entries with the same primary key value (or more accurately, with the same [sorting key](mergetree.md) value).
 

docs/en/engines/table_engines/mergetree_family/replication.md

@@ -186,7 +186,7 @@ An alternative recovery option is to delete information about the lost replica f
 
 There is no restriction on network bandwidth during recovery. Keep this in mind if you are restoring many replicas at once.
 
-## Converting From Mergetree To Replicatedmergetree {#converting-from-mergetree-to-replicatedmergetree}
+## Converting From MergeTree To ReplicatedMergeTree {#converting-from-mergetree-to-replicatedmergetree}
 
 We use the term `MergeTree` to refer to all table engines in the `MergeTree family`, the same as for `ReplicatedMergeTree`.
 
@@ -198,7 +198,7 @@ Rename the existing MergeTree table, then create a `ReplicatedMergeTree` table w
 Move the data from the old table to the `detached` subdirectory inside the directory with the new table data (`/var/lib/clickhouse/data/db_name/table_name/`).
 Then run `ALTER TABLE ATTACH PARTITION` on one of the replicas to add these data parts to the working set.
 
-## Converting From Replicatedmergetree To Mergetree {#converting-from-replicatedmergetree-to-mergetree}
+## Converting From ReplicatedMergeTree To MergeTree {#converting-from-replicatedmergetree-to-mergetree}
 
 Create a MergeTree table with a different name. Move all the data from the directory with the `ReplicatedMergeTree` table data to the new table’s data directory. Then delete the `ReplicatedMergeTree` table and restart the server.
 

docs/en/engines/table_engines/mergetree_family/summingmergetree.md

@@ -3,7 +3,7 @@ toc_priority: 34
 toc_title: SummingMergeTree
 ---
 
-# Summingmergetree {#summingmergetree}
+# SummingMergeTree {#summingmergetree}
 
 The engine inherits from [MergeTree](mergetree.md#table_engines-mergetree). The difference is that when merging data parts for `SummingMergeTree` tables ClickHouse replaces all the rows with the same primary key (or more accurately, with the same [sorting key](mergetree.md)) with one row which contains summarized values for the columns with the numeric data type. If the sorting key is composed in a way that a single key value corresponds to large number of rows, this significantly reduces storage volume and speeds up data selection.
 
@@ -94,7 +94,7 @@ SELECT key, sum(value) FROM summtt GROUP BY key
 
 ## Data Processing {#data-processing}
 
-When data are inserted into a table, they are saved as-is. Clickhouse merges the inserted parts of data periodically and this is when rows with the same primary key are summed and replaced with one for each resulting part of data.
+When data are inserted into a table, they are saved as-is. ClickHouse merges the inserted parts of data periodically and this is when rows with the same primary key are summed and replaced with one for each resulting part of data.
 
 ClickHouse can merge the data parts so that different resulting parts of data cat consist rows with the same primary key, i.e. the summation will be incomplete. Therefore (`SELECT`) an aggregate function [sum()](../../../sql_reference/aggregate_functions/reference.md#agg_function-sum) and `GROUP BY` clause should be used in a query as described in the example above.
 

docs/en/engines/table_engines/mergetree_family/versionedcollapsingmergetree.md

@@ -3,7 +3,7 @@ toc_priority: 37
 toc_title: VersionedCollapsingMergeTree
 ---
 
-# Versionedcollapsingmergetree {#versionedcollapsingmergetree}
+# VersionedCollapsingMergeTree {#versionedcollapsingmergetree}
 
 This engine:
 

docs/en/engines/table_engines/special/file.md

@@ -14,7 +14,7 @@ Usage examples:
 -   Convert data from one format to another.
 -   Updating data in ClickHouse via editing a file on a disk.
 
-## Usage In Clickhouse Server {#usage-in-clickhouse-server}
+## Usage In ClickHouse Server {#usage-in-clickhouse-server}
 
 ``` sql
 File(Format)
@@ -65,7 +65,7 @@ SELECT * FROM file_engine_table
 └──────┴───────┘
 ```
 
-## Usage In Clickhouse-local {#usage-in-clickhouse-local}
+## Usage In ClickHouse-local {#usage-in-clickhouse-local}
 
 In [clickhouse-local](../../../operations/utilities/clickhouse-local.md) File engine accepts file path in addition to `Format`. Default input/output streams can be specified using numeric or human-readable names like `0` or `stdin`, `1` or `stdout`.
 **Example:**

docs/en/engines/table_engines/special/generate.md

@@ -12,7 +12,7 @@ Usage examples:
 -   Use in test to populate reproducible large table.
 -   Generate random input for fuzzing tests.
 
-## Usage In Clickhouse Server {#usage-in-clickhouse-server}
+## Usage In ClickHouse Server {#usage-in-clickhouse-server}
 
 ``` sql
 ENGINE = GenerateRandom(random_seed, max_string_length, max_array_length)

docs/en/engines/table_engines/special/url.md

@@ -8,7 +8,7 @@ toc_title: URL
 Manages data on a remote HTTP/HTTPS server. This engine is similar
 to the [File](file.md) engine.
 
-## Using the Engine In the Clickhouse Server {#using-the-engine-in-the-clickhouse-server}
+## Using the Engine In the ClickHouse Server {#using-the-engine-in-the-clickhouse-server}
 
 The `format` must be one that ClickHouse can use in
 `SELECT` queries and, if necessary, in `INSERTs`. For the full list of supported formats, see

docs/en/faq/index.md

@@ -3,3 +3,4 @@ toc_folder_title: F.A.Q.
 toc_priority: 76
 ---
 
+

docs/en/getting_started/install.md

@@ -69,7 +69,7 @@ sudo yum install clickhouse-server clickhouse-client
 
 You can also download and install packages manually from here: https://repo.clickhouse.tech/rpm/stable/x86\_64.
 
-### From tgz archives {#from-tgz-archives}
+### From Tgz Archives {#from-tgz-archives}
 
 It is recommended to use official pre-compiled `tgz` archives for all Linux distributions, where installation of `deb` or `rpm` packages is not possible.
 

docs/en/getting_started/playground.md

@@ -32,7 +32,7 @@ You can make queries to playground using any HTTP client, for example [curl](htt
 More information about software products that support ClickHouse is available [here](../interfaces/index.md).
 
 | Parameter | Value                                 |
-|:------|:------------------------|
+|:----------|:--------------------------------------|
 | Endpoint  | https://play-api.clickhouse.tech:8443 |
 | User      | `playground`                          |
 | Password  | `clickhouse`                          |

docs/en/interfaces/formats.md

@@ -11,7 +11,7 @@ results of a `SELECT`, and to perform `INSERT`s into a file-backed table.
 The supported formats are:
 
 | Format                                                          | Input | Output |
-|---------------------------------------|-----|------|
+|-----------------------------------------------------------------|-------|--------|
 | [TabSeparated](#tabseparated)                                   | ✔     | ✔      |
 | [TabSeparatedRaw](#tabseparatedraw)                             | ✗     | ✔      |
 | [TabSeparatedWithNames](#tabseparatedwithnames)                 | ✔     | ✔      |
@@ -993,21 +993,21 @@ ClickHouse Avro format supports reading and writing [Avro data files](http://avr
 
 The table below shows supported data types and how they match ClickHouse [data types](../sql_reference/data_types/index.md) in `INSERT` and `SELECT` queries.
 
-| Avro data type `INSERT`                     | ClickHouse data type                                                                      | Avro data type `SELECT`      |
-|---------------------------|-------------------------------------------------------|------------------|
+| Avro data type `INSERT`                     | ClickHouse data type                                                                                                  | Avro data type `SELECT`      |
+|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------------|
 | `boolean`, `int`, `long`, `float`, `double` | [Int(8\|16\|32)](../sql_reference/data_types/int_uint.md), [UInt(8\|16\|32)](../sql_reference/data_types/int_uint.md) | `int`                        |
 | `boolean`, `int`, `long`, `float`, `double` | [Int64](../sql_reference/data_types/int_uint.md), [UInt64](../sql_reference/data_types/int_uint.md)                   | `long`                       |
-| `boolean`, `int`, `long`, `float`, `double` | [Float32](../sql_reference/data_types/float.md)                                                         | `float`                      |
-| `boolean`, `int`, `long`, `float`, `double` | [Float64](../sql_reference/data_types/float.md)                                                         | `double`                     |
-| `bytes`, `string`, `fixed`, `enum`          | [String](../sql_reference/data_types/string.md)                                                         | `bytes`                      |
-| `bytes`, `string`, `fixed`                  | [FixedString(N)](../sql_reference/data_types/fixedstring.md)                                            | `fixed(N)`                   |
-| `enum`                                      | [Enum(8\|16)](../sql_reference/data_types/enum.md)                                                      | `enum`                       |
-| `array(T)`                                  | [Array(T)](../sql_reference/data_types/array.md)                                                        | `array(T)`                   |
-| `union(null, T)`, `union(T, null)`          | [Nullable(T)](../sql_reference/data_types/date.md)                                                      | `union(null, T)`             |
-| `null`                                      | [Nullable(Nothing)](../sql_reference/data_types/special_data_types/nothing.md)                          | `null`                       |
-| `int (date)` \*                             | [Date](../sql_reference/data_types/date.md)                                                             | `int (date)` \*              |
-| `long (timestamp-millis)` \*                | [DateTime64(3)](../sql_reference/data_types/datetime.md)                                                | `long (timestamp-millis)` \* |
-| `long (timestamp-micros)` \*                | [DateTime64(6)](../sql_reference/data_types/datetime.md)                                                | `long (timestamp-micros)` \* |
+| `boolean`, `int`, `long`, `float`, `double` | [Float32](../sql_reference/data_types/float.md)                                                                       | `float`                      |
+| `boolean`, `int`, `long`, `float`, `double` | [Float64](../sql_reference/data_types/float.md)                                                                       | `double`                     |
+| `bytes`, `string`, `fixed`, `enum`          | [String](../sql_reference/data_types/string.md)                                                                       | `bytes`                      |
+| `bytes`, `string`, `fixed`                  | [FixedString(N)](../sql_reference/data_types/fixedstring.md)                                                          | `fixed(N)`                   |
+| `enum`                                      | [Enum(8\|16)](../sql_reference/data_types/enum.md)                                                                    | `enum`                       |
+| `array(T)`                                  | [Array(T)](../sql_reference/data_types/array.md)                                                                      | `array(T)`                   |
+| `union(null, T)`, `union(T, null)`          | [Nullable(T)](../sql_reference/data_types/date.md)                                                                    | `union(null, T)`             |
+| `null`                                      | [Nullable(Nothing)](../sql_reference/data_types/special_data_types/nothing.md)                                        | `null`                       |
+| `int (date)` \*                             | [Date](../sql_reference/data_types/date.md)                                                                           | `int (date)` \*              |
+| `long (timestamp-millis)` \*                | [DateTime64(3)](../sql_reference/data_types/datetime.md)                                                              | `long (timestamp-millis)` \* |
+| `long (timestamp-micros)` \*                | [DateTime64(6)](../sql_reference/data_types/datetime.md)                                                              | `long (timestamp-micros)` \* |
 
 \* [Avro logical types](http://avro.apache.org/docs/current/spec.html#Logical+Types)
 
@@ -1101,8 +1101,8 @@ SELECT * FROM topic1_stream;
 
 The table below shows supported data types and how they match ClickHouse [data types](../sql_reference/data_types/index.md) in `INSERT` and `SELECT` queries.
 
-| Parquet data type (`INSERT`) | ClickHouse data type                        | Parquet data type (`SELECT`) |
-|------------------|---------------------------|------------------|
+| Parquet data type (`INSERT`) | ClickHouse data type                                      | Parquet data type (`SELECT`) |
+|------------------------------|-----------------------------------------------------------|------------------------------|
 | `UINT8`, `BOOL`              | [UInt8](../sql_reference/data_types/int_uint.md)          | `UINT8`                      |
 | `INT8`                       | [Int8](../sql_reference/data_types/int_uint.md)           | `INT8`                       |
 | `UINT16`                     | [UInt16](../sql_reference/data_types/int_uint.md)         | `UINT16`                     |
@@ -1149,8 +1149,8 @@ To exchange data with Hadoop, you can use [HDFS table engine](../engines/table_e
 
 The table below shows supported data types and how they match ClickHouse [data types](../sql_reference/data_types/index.md) in `INSERT` queries.
 
-| ORC data type (`INSERT`) | ClickHouse data type                  |
-|----------------|-------------------------|
+| ORC data type (`INSERT`) | ClickHouse data type                                |
+|--------------------------|-----------------------------------------------------|
 | `UINT8`, `BOOL`          | [UInt8](../sql_reference/data_types/int_uint.md)    |
 | `INT8`                   | [Int8](../sql_reference/data_types/int_uint.md)     |
 | `UINT16`                 | [UInt16](../sql_reference/data_types/int_uint.md)   |

docs/en/interfaces/http.md

@@ -286,31 +286,35 @@ $ curl -sS "<address>?param_id=2&param_phrase=test" -d "SELECT * FROM table WHER
 ## Predefined HTTP Interface {#predefined_http_interface}
 
 ClickHouse supports specific queries through the HTTP interface. For example, you can write data to a table as follows:
- 
-```bash
+
+``` bash
 $ echo '(4),(5),(6)' | curl 'http://localhost:8123/?query=INSERT%20INTO%20t%20VALUES' --data-binary @-
 ```
 
-ClickHouse also supports Predefined HTTP Interface which can help you more easy integration with third party tools like [Prometheus exporter](https://github.com/percona-lab/clickhouse_exporter). 
+ClickHouse also supports Predefined HTTP Interface which can help you more easy integration with third party tools like [Prometheus exporter](https://github.com/percona-lab/clickhouse_exporter).
 
 Example:
- 
-*  First of all, add this section to server configuration file:
- 
+
+-   First of all, add this section to server configuration file:
+
+<!-- -->
+
 ``` xml
 <http_handlers>
   <predefine_query_handler>
-	  <url>/metrics</url>
-	    <method>GET</method>
-	    <queries>
-	        <query>SELECT * FROM system.metrics LIMIT 5 FORMAT Template SETTINGS format_template_resultset = 'prometheus_template_output_format_resultset', format_template_row = 'prometheus_template_output_format_row', format_template_rows_between_delimiter = '\n'</query>
-	    </queries>
+      <url>/metrics</url>
+        <method>GET</method>
+        <queries>
+            <query>SELECT * FROM system.metrics LIMIT 5 FORMAT Template SETTINGS format_template_resultset = 'prometheus_template_output_format_resultset', format_template_row = 'prometheus_template_output_format_row', format_template_rows_between_delimiter = '\n'</query>
+        </queries>
   </predefine_query_handler>
 </http_handlers>
 ```
- 
-* You can now request the url directly for data in the Prometheus format:
- 
+
+-   You can now request the url directly for data in the Prometheus format:
+
+<!-- -->
+
 ``` bash
 curl -vvv 'http://localhost:8123/metrics'
 *   Trying ::1...
@@ -319,7 +323,7 @@ curl -vvv 'http://localhost:8123/metrics'
 > Host: localhost:8123
 > User-Agent: curl/7.47.0
 > Accept: */*
-> 
+>
 < HTTP/1.1 200 OK
 < Date: Wed, 27 Nov 2019 08:54:25 GMT
 < Connection: Keep-Alive
@@ -329,7 +333,7 @@ curl -vvv 'http://localhost:8123/metrics'
 < X-ClickHouse-Query-Id: f39235f6-6ed7-488c-ae07-c7ceafb960f6
 < Keep-Alive: timeout=3
 < X-ClickHouse-Summary: {"read_rows":"0","read_bytes":"0","written_rows":"0","written_bytes":"0","total_rows_to_read":"0"}
-< 
+<
 # HELP "Query" "Number of executing queries"
 # TYPE "Query" counter
 "Query" 1
@@ -337,19 +341,19 @@ curl -vvv 'http://localhost:8123/metrics'
 # HELP "Merge" "Number of executing background merges"
 # TYPE "Merge" counter
 "Merge" 0
- 
+
 # HELP "PartMutation" "Number of mutations (ALTER DELETE/UPDATE)"
 # TYPE "PartMutation" counter
 "PartMutation" 0
- 
+
 # HELP "ReplicatedFetch" "Number of data parts being fetched from replica"
 # TYPE "ReplicatedFetch" counter
 "ReplicatedFetch" 0
- 
+
 # HELP "ReplicatedSend" "Number of data parts being sent to replicas"
 # TYPE "ReplicatedSend" counter
 "ReplicatedSend" 0
- 
+
 * Connection #0 to host localhost left intact
 ```
 
@@ -357,26 +361,24 @@ As you can see from the example, if `<http_handlers>` is configured in the confi
 
 Now `<http_handlers>` can configure `<root_handler>`, `<ping_handler>`, `<replicas_status_handler>`, `<dynamic_query_handler>` and `<no_handler_description>` .
 
-## root_handler
+## root\_handler {#root_handler}
 
- `<root_handler>` returns the specified content for the root path request. The specific return content is configured by `http_server_default_response` in config.xml. if not specified, return **Ok.** 
+`<root_handler>` returns the specified content for the root path request. The specific return content is configured by `http_server_default_response` in config.xml. if not specified, return **Ok.**
 
 `http_server_default_response` is not defined and an HTTP request is sent to ClickHouse. The result is as follows:
 
-```xml
+``` xml
 <http_handlers>
     <root_handler/>
 </http_handlers>
 ```
 
-```
-$ curl 'http://localhost:8123'
-Ok.
-```
+    $ curl 'http://localhost:8123'
+    Ok.
 
 `http_server_default_response` is defined and an HTTP request is sent to ClickHouse. The result is as follows:
 
-```xml
+``` xml
 <http_server_default_response><![CDATA[<html ng-app="SMI2"><head><base href="http://ui.tabix.io/"></head><body><div ui-view="" class="content-ui"></div><script src="http://loader.tabix.io/master.js"></script></body></html>]]></http_server_default_response>
 
 <http_handlers>
@@ -384,35 +386,33 @@ Ok.
 </http_handlers>
 ```
 
-```
-$ curl 'http://localhost:8123'
-<html ng-app="SMI2"><head><base href="http://ui.tabix.io/"></head><body><div ui-view="" class="content-ui"></div><script src="http://loader.tabix.io/master.js"></script></body></html>% 
-```
+    $ curl 'http://localhost:8123'
+    <html ng-app="SMI2"><head><base href="http://ui.tabix.io/"></head><body><div ui-view="" class="content-ui"></div><script src="http://loader.tabix.io/master.js"></script></body></html>%
 
-## ping_handler
+## ping\_handler {#ping_handler}
 
 `<ping_handler>` can be used to probe the health of the current ClickHouse Server. When the ClickHouse HTTP Server is normal, accessing ClickHouse through `<ping_handler>` will return **Ok.**.
 
 Example:
 
-```xml
+``` xml
 <http_handlers>
     <ping_handler>/ping</ping_handler>
 </http_handlers>
 ```
 
-```bash
+``` bash
 $ curl 'http://localhost:8123/ping'
 Ok.
 ```
 
-## replicas_status_handler
+## replicas\_status\_handler {#replicas_status_handler}
 
-`<replicas_status_handler>` is used to detect the state of the replica node and return **Ok.** if the replica node has no delay. If there is a delay, return the specific delay. The value of `<replicas_status_handler>`  supports customization. If you do not specify `<replicas_status_handler>`, ClickHouse default setting `<replicas_status_handler>` is **/replicas_status**.
+`<replicas_status_handler>` is used to detect the state of the replica node and return **Ok.** if the replica node has no delay. If there is a delay, return the specific delay. The value of `<replicas_status_handler>` supports customization. If you do not specify `<replicas_status_handler>`, ClickHouse default setting `<replicas_status_handler>` is **/replicas\_status**.
 
 Example:
 
-```xml
+``` xml
 <http_handlers>
     <replicas_status_handler>/replicas_status</replicas_status_handler>
 </http_handlers>
@@ -420,90 +420,90 @@ Example:
 
 No delay case:
 
-```bash
+``` bash
 $ curl 'http://localhost:8123/replicas_status'
 Ok.
 ```
 
 Delayed case:
 
-```bash
+``` bash
 $ curl 'http://localhost:8123/replicas_status'
 db.stats:  Absolute delay: 22. Relative delay: 22.
 ```
 
-## predefined_query_handler
+## predefined\_query\_handler {#predefined_query_handler}
 
 You can configure `<method>`, `<headers>`, `<url>` and `<queries>` in `<predefined_query_handler>`.
 
 `<method>` is responsible for matching the method part of the HTTP request. `<method>` fully conforms to the definition of [method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods) in the HTTP protocol. It is an optional configuration. If it is not defined in the configuration file, it does not match the method portion of the HTTP request
 
-`<url>`  is responsible for matching the url part of the HTTP request. It is compatible with [RE2](https://github.com/google/re2)'s regular expressions. It is an optional configuration. If it is not defined in the configuration file, it does not match the url portion of the HTTP request
+`<url>` is responsible for matching the url part of the HTTP request. It is compatible with [RE2](https://github.com/google/re2)’s regular expressions. It is an optional configuration. If it is not defined in the configuration file, it does not match the url portion of the HTTP request
 
-`<headers>` is responsible for matching the header part of the HTTP request. It is compatible with RE2's regular expressions. It is an optional configuration. If it is not defined in the configuration file, it does not match the header portion of the HTTP request
+`<headers>` is responsible for matching the header part of the HTTP request. It is compatible with RE2’s regular expressions. It is an optional configuration. If it is not defined in the configuration file, it does not match the header portion of the HTTP request
 
 `<queries>` value is a predefined query of `<predefined_query_handler>`, which is executed by ClickHouse when an HTTP request is matched and the result of the query is returned. It is a must configuration.
 
-`<predefined_query_handler>` supports setting Settings and query_params values. 
+`<predefined_query_handler>` supports setting Settings and query\_params values.
 
 The following example defines the values of `max_threads` and `max_alter_threads` settings, then queries the system table to check whether these settings were set successfully.
 
 Example:
 
-```xml
+``` xml
 <root_handlers>
-	<predefined_query_handler>
-	    <method>GET</method>
-	    <headers>
-	        <XXX>TEST_HEADER_VALUE</XXX>
-	        <PARAMS_XXX><![CDATA[(?P<name_1>[^/]+)(/(?P<name_2>[^/]+))?]]></PARAMS_XXX>
-	    </headers>
-	    <url><![CDATA[/query_param_with_url/\w+/(?P<name_1>[^/]+)(/(?P<name_2>[^/]+))?]]></url>
-	    <queries>
-	        <query>SELECT value FROM system.settings WHERE name = {name_1:String}</query>
-	        <query>SELECT name, value FROM system.settings WHERE name = {name_2:String}</query>
-	    </queries>
-	</predefined_query_handler>
+    <predefined_query_handler>
+        <method>GET</method>
+        <headers>
+            <XXX>TEST_HEADER_VALUE</XXX>
+            <PARAMS_XXX><![CDATA[(?P<name_1>[^/]+)(/(?P<name_2>[^/]+))?]]></PARAMS_XXX>
+        </headers>
+        <url><![CDATA[/query_param_with_url/\w+/(?P<name_1>[^/]+)(/(?P<name_2>[^/]+))?]]></url>
+        <queries>
+            <query>SELECT value FROM system.settings WHERE name = {name_1:String}</query>
+            <query>SELECT name, value FROM system.settings WHERE name = {name_2:String}</query>
+        </queries>
+    </predefined_query_handler>
 </root_handlers>
 ```
 
-```bash
+``` bash
 $ curl -H 'XXX:TEST_HEADER_VALUE' -H 'PARAMS_XXX:max_threads' 'http://localhost:8123/query_param_with_url/1/max_threads/max_alter_threads?max_threads=1&max_alter_threads=2'
 1
-max_alter_threads	2
+max_alter_threads   2
 ```
 
 !!! note "Note"
     In one `<predefined_query_handler>`, one `<queries>` only supports one `<query>` of an insert type.
 
-## dynamic_query_handler
+## dynamic\_query\_handler {#dynamic_query_handler}
 
-`<dynamic_query_handler>` than `<predefined_query_handler>` increased  `<query_param_name>` .
+`<dynamic_query_handler>` than `<predefined_query_handler>` increased `<query_param_name>` .
 
 ClickHouse extracts and executes the value corresponding to the `<query_param_name>` value in the url of the HTTP request.
 ClickHouse default setting `<query_param_name>` is `/query` . It is an optional configuration. If there is no definition in the configuration file, the param is not passed in.
 
-To experiment with this functionality, the example defines the values of max_threads and max_alter_threads and queries whether the Settings were set successfully.
+To experiment with this functionality, the example defines the values of max\_threads and max\_alter\_threads and queries whether the Settings were set successfully.
 The difference is that in `<predefined_query_handler>`, query is wrote in the configuration file. But in `<dynamic_query_handler>`, query is written in the form of param of the HTTP request.
 
 Example:
 
-```xml
+``` xml
 <root_handlers>
-	<dynamic_query_handler>
-	    <headers>
-	        <XXX>TEST_HEADER_VALUE_DYNAMIC</XXX>
-	        <PARAMS_XXX><![CDATA[(?P<param_name_1>[^/]+)(/(?P<param_name_2>[^/]+))?]]></PARAMS_XXX>
-	    </headers>
-	    <query_param_name>query_param</query_param_name>
-	</dynamic_query_handler>
+    <dynamic_query_handler>
+        <headers>
+            <XXX>TEST_HEADER_VALUE_DYNAMIC</XXX>
+            <PARAMS_XXX><![CDATA[(?P<param_name_1>[^/]+)(/(?P<param_name_2>[^/]+))?]]></PARAMS_XXX>
+        </headers>
+        <query_param_name>query_param</query_param_name>
+    </dynamic_query_handler>
 </root_handlers>
 ```
 
-```bash
+``` bash
 $ curl  -H 'XXX:TEST_HEADER_VALUE_DYNAMIC' -H 'PARAMS_XXX:max_threads' 'http://localhost:8123/?query_param=SELECT%20value%20FROM%20system.settings%20where%20name%20=%20%7Bname_1:String%7D%20OR%20name%20=%20%7Bname_2:String%7D&max_threads=1&max_alter_threads=2&param_name_2=max_alter_threads'
 1
 2
 ```
 
-[Original article](https://clickhouse.tech/docs/en/interfaces/http_interface/) <!--hide-->
+[Original article](https://clickhouse.tech/docs/en/interfaces/http_interface/) <!--hide-->

docs/en/interfaces/mysql.md

@@ -3,7 +3,7 @@ toc_priority: 20
 toc_title: MySQL Interface
 ---
 
-# MySQL interface {#mysql-interface}
+# MySQL Interface {#mysql-interface}
 
 ClickHouse supports MySQL wire protocol. It can be enabled by [mysql\_port](../operations/server_configuration_parameters/settings.md#server_configuration_parameters-mysql_port) setting in configuration file:
 

docs/en/interfaces/third-party/client_libraries.md

@@ -37,7 +37,7 @@ toc_title: Client Libraries
     -   [clickhouse-activerecord](https://github.com/PNixx/clickhouse-activerecord)
 -   R
     -   [clickhouse-r](https://github.com/hannesmuehleisen/clickhouse-r)
-    -   [RClickhouse](https://github.com/IMSMWU/RClickhouse)
+    -   [RClickHouse](https://github.com/IMSMWU/RClickHouse)
 -   Java
     -   [clickhouse-client-java](https://github.com/VirtusAI/clickhouse-client-java)
     -   [clickhouse-client](https://github.com/Ecwid/clickhouse-client)

docs/en/interfaces/third-party/integrations.md

@@ -74,7 +74,7 @@ toc_title: Integrations
         -   [pandahouse](https://github.com/kszucs/pandahouse)
 -   R
     -   [dplyr](https://db.rstudio.com/dplyr/)
-        -   [RClickhouse](https://github.com/IMSMWU/RClickhouse) (uses [clickhouse-cpp](https://github.com/artpaul/clickhouse-cpp))
+        -   [RClickHouse](https://github.com/IMSMWU/RClickHouse) (uses [clickhouse-cpp](https://github.com/artpaul/clickhouse-cpp))
 -   Java
     -   [Hadoop](http://hadoop.apache.org)
         -   [clickhouse-hdfs-loader](https://github.com/jaykelin/clickhouse-hdfs-loader) (uses [JDBC](../../sql_reference/table_functions/jdbc.md))

docs/en/introduction/adopters.md

@@ -9,7 +9,7 @@ toc_title: Adopters
     The following list of companies using ClickHouse and their success stories is assembled from public sources, thus might differ from current reality. We’d appreciate it if you share the story of adopting ClickHouse in your company and [add it to the list](https://github.com/ClickHouse/ClickHouse/edit/master/docs/en/introduction/adopters.md), but please make sure you won’t have any NDA issues by doing so. Providing updates with publications from other companies is also useful.
 
 | Company                                                                     | Industry                        | Usecase               | Cluster Size                                               | (Un)Compressed Data Size<abbr title="of single replica"><sup>\*</sup></abbr> | Reference                                                                                                                                                                                                               |
-|-----------------------------------------------|---------------------|---------------|------------------------------------|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
+|-----------------------------------------------------------------------------|---------------------------------|-----------------------|------------------------------------------------------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | [2gis](https://2gis.ru)                                                     | Maps                            | Monitoring            | —                                                          | —                                                                            | [Talk in Russian, July 2019](https://youtu.be/58sPkXfq6nw)                                                                                                                                                              |
 | [Aloha Browser](https://alohabrowser.com/)                                  | Mobile App                      | Browser backend       | —                                                          | —                                                                            | [Slides in Russian, May 2019](https://github.com/yandex/clickhouse-presentations/blob/master/meetup22/aloha.pdf)                                                                                                        |
 | [Amadeus](https://amadeus.com/)                                             | Travel                          | Analytics             | —                                                          | —                                                                            | [Press Release, April 2018](https://www.altinity.com/blog/2018/4/5/amadeus-technologies-launches-investment-and-insights-tool-based-on-machine-learning-and-strategy-algorithms)                                        |
@@ -20,7 +20,7 @@ toc_title: Adopters
 | [Bloomberg](https://www.bloomberg.com/)                                     | Finance, Media                  | Monitoring            | 102 servers                                                | —                                                                            | [Slides, May 2018](https://www.slideshare.net/Altinity/http-analytics-for-6m-requests-per-second-using-clickhouse-by-alexander-bocharov)                                                                                |
 | [Bloxy](https://bloxy.info)                                                 | Blockchain                      | Analytics             | —                                                          | —                                                                            | [Slides in Russian, August 2018](https://github.com/ClickHouse/clickhouse-presentations/blob/master/meetup17/4_bloxy.pptx)                                                                                              |
 | `Dataliance/UltraPower`                                                     | Telecom                         | Analytics             | —                                                          | —                                                                            | [Slides in Chinese, January 2018](https://github.com/ClickHouse/clickhouse-presentations/blob/master/meetup12/telecom.pdf)                                                                                              |
-| [CARTO](https://carto.com/)                                                 | Business Intelligence           | Geo analytics         | —                                                          | —                                                                            | [Geospatial processing with Clickhouse](https://carto.com/blog/geospatial-processing-with-clickhouse/)                                                                                                                  |
+| [CARTO](https://carto.com/)                                                 | Business Intelligence           | Geo analytics         | —                                                          | —                                                                            | [Geospatial processing with ClickHouse](https://carto.com/blog/geospatial-processing-with-clickhouse/)                                                                                                                  |
 | [CERN](http://public.web.cern.ch/public/)                                   | Research                        | Experiment            | —                                                          | —                                                                            | [Press release, April 2012](https://www.yandex.com/company/press_center/press_releases/2012/2012-04-10/)                                                                                                                |
 | [Cisco](http://cisco.com/)                                                  | Networking                      | Traffic analysis      | —                                                          | —                                                                            | [Lightning talk, October 2019](https://youtu.be/-hI1vDR2oPY?t=5057)                                                                                                                                                     |
 | [Citadel Securities](https://www.citadelsecurities.com/)                    | Finance                         | —                     | —                                                          | —                                                                            | [Contribution, March 2019](https://github.com/ClickHouse/ClickHouse/pull/4774)                                                                                                                                          |
@@ -64,7 +64,7 @@ toc_title: Adopters
 | [Splunk](https://www.splunk.com/)                                           | Business Analytics              | Main product          | —                                                          | —                                                                            | [Slides in English, January 2018](https://github.com/ClickHouse/clickhouse-presentations/blob/master/meetup12/splunk.pdf)                                                                                               |
 | [Spotify](https://www.spotify.com)                                          | Music                           | Experimentation       | —                                                          | —                                                                            | [Slides, July 2018](https://www.slideshare.net/glebus/using-clickhouse-for-experimentation-104247173)                                                                                                                   |
 | [Tencent](https://www.tencent.com)                                          | Big Data                        | Data processing       | —                                                          | —                                                                            | [Slides in Chinese, October 2018](https://github.com/ClickHouse/clickhouse-presentations/blob/master/meetup19/5.%20ClickHouse大数据集群应用_李俊飞腾讯网媒事业部.pdf)                                                   |
-| [Uber](https://www.uber.com)                                                | Taxi                            | Logging               | —                                                          | —                                                                            | [Slides, February 2020](https://presentations.clickhouse.tech/meetup40/uber.pdf)                                                                                                                                          |
+| [Uber](https://www.uber.com)                                                | Taxi                            | Logging               | —                                                          | —                                                                            | [Slides, February 2020](https://presentations.clickhouse.tech/meetup40/uber.pdf)                                                                                                                                        |
 | [VKontakte](https://vk.com)                                                 | Social Network                  | Statistics, Logging   | —                                                          | —                                                                            | [Slides in Russian, August 2018](https://github.com/ClickHouse/clickhouse-presentations/blob/master/meetup17/3_vk.pdf)                                                                                                  |
 | [Wisebits](https://wisebits.com/)                                           | IT Solutions                    | Analytics             | —                                                          | —                                                                            | [Slides in Russian, May 2019](https://github.com/ClickHouse/clickhouse-presentations/blob/master/meetup22/strategies.pdf)                                                                                               |
 | [Xiaoxin Tech.](https://www.xiaoheiban.cn/)                                 | Education                       | Common purpose        | —                                                          | —                                                                            | [Slides in English, November 2019](https://github.com/ClickHouse/clickhouse-presentations/blob/master/meetup33/sync-clickhouse-with-mysql-mongodb.pptx)                                                                 |

docs/en/introduction/distinctive_features.md

@@ -60,7 +60,7 @@ ClickHouse provides various ways to trade accuracy for performance:
 2.  Running a query based on a part (sample) of data and getting an approximated result. In this case, proportionally less data is retrieved from the disk.
 3.  Running an aggregation for a limited number of random keys, instead of for all keys. Under certain conditions for key distribution in the data, this provides a reasonably accurate result while using fewer resources.
 
-## Data replication and data integrity support {#data-replication-and-data-integrity-support}
+## Data Replication and Data Integrity Support {#data-replication-and-data-integrity-support}
 
 ClickHouse uses asynchronous multi-master replication. After being written to any available replica, all the remaining replicas retrieve their copy in the background. The system maintains identical data on different replicas. Recovery after most failures is performed automatically, or semi-automatically in complex cases.
 

docs/en/introduction/features_considered_disadvantages.md

@@ -3,7 +3,7 @@ toc_priority: 5
 toc_title: ClickHouse Features that Can Be Considered Disadvantages
 ---
 
-# ClickHouse Features that Can be Considered Disadvantages {#clickhouse-features-that-can-be-considered-disadvantages}
+# ClickHouse Features that Can Be Considered Disadvantages {#clickhouse-features-that-can-be-considered-disadvantages}
 
 1.  No full-fledged transactions.
 2.  Lack of ability to modify or delete already inserted data with high rate and low latency. There are batch deletes and updates available to clean up or modify data, for example to comply with [GDPR](https://gdpr-info.eu).

docs/en/introduction/index.md

@@ -3,3 +3,4 @@ toc_folder_title: Introduction
 toc_priority: 1
 ---
 
+

docs/en/operations/backup.md

@@ -28,7 +28,7 @@ Some local filesystems provide snapshot functionality (for example, [ZFS](https:
 
 For smaller volumes of data, a simple `INSERT INTO ... SELECT ...` to remote tables might work as well.
 
-## Manipulations With Parts {#manipulations-with-parts}
+## Manipulations with Parts {#manipulations-with-parts}
 
 ClickHouse allows using the `ALTER TABLE ... FREEZE PARTITION ...` query to create a local copy of table partitions. This is implemented using hardlinks to the `/var/lib/clickhouse/shadow/` folder, so it usually does not consume extra disk space for old data. The created copies of files are not handled by ClickHouse server, so you can just leave them there: you will have a simple backup that doesn’t require any additional external system, but it will still be prone to hardware issues. For this reason, it’s better to remotely copy them to another location and then remove the local copies. Distributed filesystems and object stores are still a good options for this, but normal attached file servers with a large enough capacity might work as well (in this case the transfer will occur via the network filesystem or maybe [rsync](https://en.wikipedia.org/wiki/Rsync)).
 

docs/en/operations/monitoring.md

@@ -22,7 +22,7 @@ It is highly recommended to set up monitoring for:
 
 -   Utilization of storage system, RAM and network.
 
-## Clickhouse Server Metrics {#clickhouse-server-metrics}
+## ClickHouse Server Metrics {#clickhouse-server-metrics}
 
 ClickHouse server has embedded instruments for self-state monitoring.
 

docs/en/operations/performance_test.md

@@ -3,7 +3,7 @@ toc_priority: 54
 toc_title: Testing Hardware
 ---
 
-# How To Test Your Hardware With ClickHouse {#how-to-test-your-hardware-with-clickhouse}
+# How to Test Your Hardware with ClickHouse {#how-to-test-your-hardware-with-clickhouse}
 
 With this instruction you can run basic ClickHouse performance test on any server without installation of ClickHouse packages.
 
@@ -24,7 +24,7 @@ With this instruction you can run basic ClickHouse performance test on any serve
       # Then do:
       chmod a+x clickhouse
 
-5.  Download configs:
+1.  Download configs:
 
 <!-- -->
 
@@ -34,7 +34,7 @@ With this instruction you can run basic ClickHouse performance test on any serve
       wget https://raw.githubusercontent.com/ClickHouse/ClickHouse/master/programs/server/config.d/path.xml -O config.d/path.xml
       wget https://raw.githubusercontent.com/ClickHouse/ClickHouse/master/programs/server/config.d/log_to_console.xml -O config.d/log_to_console.xml
 
-6.  Download benchmark files:
+1.  Download benchmark files:
 
 <!-- -->
 
@@ -42,7 +42,7 @@ With this instruction you can run basic ClickHouse performance test on any serve
       chmod a+x benchmark-new.sh
       wget https://raw.githubusercontent.com/ClickHouse/ClickHouse/master/benchmark/clickhouse/queries.sql
 
-7.  Download test data according to the [Yandex.Metrica dataset](../getting_started/example_datasets/metrica.md) instruction (“hits” table containing 100 million rows).
+1.  Download test data according to the [Yandex.Metrica dataset](../getting_started/example_datasets/metrica.md) instruction (“hits” table containing 100 million rows).
 
 <!-- -->
 
@@ -50,31 +50,31 @@ With this instruction you can run basic ClickHouse performance test on any serve
       tar xvf hits_100m_obfuscated_v1.tar.xz -C .
       mv hits_100m_obfuscated_v1/* .
 
-8.  Run the server:
+1.  Run the server:
 
 <!-- -->
 
       ./clickhouse server
 
-9.  Check the data: ssh to the server in another terminal
+1.  Check the data: ssh to the server in another terminal
 
 <!-- -->
 
       ./clickhouse client --query "SELECT count() FROM hits_100m_obfuscated"
       100000000
 
-10.  Edit the benchmark-new.sh, change “clickhouse-client” to “./clickhouse client” and add “–max\_memory\_usage 100000000000” parameter.
+1.  Edit the benchmark-new.sh, change “clickhouse-client” to “./clickhouse client” and add “–max\_memory\_usage 100000000000” parameter.
 
 <!-- -->
 
       mcedit benchmark-new.sh
 
-11.  Run the benchmark:
+1.  Run the benchmark:
 
 <!-- -->
 
       ./benchmark-new.sh hits_100m_obfuscated
 
-12.  Send the numbers and the info about your hardware configuration to clickhouse-feedback@yandex-team.com
+1.  Send the numbers and the info about your hardware configuration to clickhouse-feedback@yandex-team.com
 
-All the results are published here: https://clickhouse.tech/benchmark_hardware.html
+All the results are published here: https://clickhouse.tech/benchmark\_hardware.html

docs/en/operations/system_tables.md

@@ -147,27 +147,68 @@ This system table is used for implementing the `SHOW DATABASES` query.
 
 Contains information about detached parts of [MergeTree](../engines/table_engines/mergetree_family/mergetree.md) tables. The `reason` column specifies why the part was detached. For user-detached parts, the reason is empty. Such parts can be attached with [ALTER TABLE ATTACH PARTITION\|PART](../sql_reference/statements/alter.md#alter_attach-partition) command. For the description of other columns, see [system.parts](#system_tables-parts). If part name is invalid, values of some columns may be `NULL`. Such parts can be deleted with [ALTER TABLE DROP DETACHED PART](../sql_reference/statements/alter.md#alter_drop-detached).
 
-## system.dictionaries {#system-dictionaries}
+## system.dictionaries {#system_tables-dictionaries}
 
-Contains information about external dictionaries.
+Contains information about [external dictionaries](../sql_reference/dictionaries/external_dictionaries/external_dicts.md).
 
 Columns:
 
--   `name` (String) — Dictionary name.
--   `type` (String) — Dictionary type: Flat, Hashed, Cache.
--   `origin` (String) — Path to the configuration file that describes the dictionary.
--   `attribute.names` (Array(String)) — Array of attribute names provided by the dictionary.
--   `attribute.types` (Array(String)) — Corresponding array of attribute types that are provided by the dictionary.
--   `has_hierarchy` (UInt8) — Whether the dictionary is hierarchical.
--   `bytes_allocated` (UInt64) — The amount of RAM the dictionary uses.
--   `hit_rate` (Float64) — For cache dictionaries, the percentage of uses for which the value was in the cache.
--   `element_count` (UInt64) — The number of items stored in the dictionary.
--   `load_factor` (Float64) — The percentage filled in the dictionary (for a hashed dictionary, the percentage filled in the hash table).
--   `creation_time` (DateTime) — The time when the dictionary was created or last successfully reloaded.
--   `last_exception` (String) — Text of the error that occurs when creating or reloading the dictionary if the dictionary couldn’t be created.
--   `source` (String) — Text describing the data source for the dictionary.
+- `database` ([String](../sql_reference/data_types/string.md)) — Name of the database containing the dictionary created by DDL query. Empty string for other dictionaries.
+- `name` ([String](../sql_reference/data_types/string.md)) — [Dictionary name](../sql_reference/dictionaries/external_dictionaries/external_dicts_dict.md).
+- `status` ([Enum8](../sql_reference/data_types/enum.md)) — Dictionary status. Possible values: 
+     - `NOT_LOADED` — Dictionary was not loaded because it was not used.
+     - `LOADED` — Dictionary loaded successfully.
+     - `FAILED` — Unable to load the dictionary as a result of an error.
+     - `LOADING` — Dictionary is loading now.
+     - `LOADED_AND_RELOADING` — Dictionary is loaded successfully, and is being reloaded right now (frequent reasons: [SYSTEM RELOAD DICTIONARY](../sql_reference/statements/system.md#query_language-system-reload-dictionary) query, timeout, dictionary config has changed).
+     - `FAILED_AND_RELOADING` — Could not load the dictionary as a result of an error and is loading now.
+- `origin` ([String](../sql_reference/data_types/string.md)) — Path to the configuration file that describes the dictionary.
+- `type` ([String](../sql_reference/data_types/string.md)) — Type of a dictionary allocation. [Storing Dictionaries in Memory](../sql_reference/dictionaries/external_dictionaries/external_dicts_dict_layout.md).
+- `key` — [Key type](../sql_reference/dictionaries/external_dictionaries/external_dicts_dict_structure.md#ext_dict_structure-key): Numeric Key ([UInt64](../sql_reference/data_types/int_uint.md#uint-ranges)) or Сomposite key ([String](../sql_reference/data_types/string.md)) — form "(type 1, type 2, ..., type n)".
+- `attribute.names` ([Array](../sql_reference/data_types/array.md)([String](../sql_reference/data_types/string.md))) — Array of [attribute names](../sql_reference/dictionaries/external_dictionaries/external_dicts_dict_structure.md#ext_dict_structure-attributes) provided by the dictionary.
+- `attribute.types`  ([Array](../sql_reference/data_types/array.md)([String](../sql_reference/data_types/string.md))) — Corresponding array of [attribute types](../sql_reference/dictionaries/external_dictionaries/external_dicts_dict_structure.md#ext_dict_structure-attributes) that are provided by the dictionary.
+- `bytes_allocated` ([UInt64](../sql_reference/data_types/int_uint.md#uint-ranges)) — Amount of RAM allocated for the dictionary.
+- `query_count` ([UInt64](../sql_reference/data_types/int_uint.md#uint-ranges)) — Number of queries since the dictionary was loaded or since the last successful reboot.
+- `hit_rate` ([Float64](../sql_reference/data_types/float.md)) — For cache dictionaries, the percentage of uses for which the value was in the cache.
+- `element_count` ([UInt64](../sql_reference/data_types/int_uint.md#uint-ranges)) — Number of items stored in the dictionary.
+- `load_factor` ([Float64](../sql_reference/data_types/float.md)) — Percentage filled in the dictionary (for a hashed dictionary, the percentage filled in the hash table).
+- `source` ([String](../sql_reference/data_types/string.md)) — Text describing the [data source](../sql_reference/dictionaries/external_dictionaries/external_dicts_dict_sources.md) for the dictionary.
+- `lifetime_min` ([UInt64](../sql_reference/data_types/int_uint.md#uint-ranges)) — Minimum [lifetime](../sql_reference/dictionaries/external_dictionaries/external_dicts_dict_lifetime.md) of the dictionary in memory, after which ClickHouse tries to reload the dictionary (if `invalidate_query` is set, then only if it has changed). Set in seconds.
+- `lifetime_max` ([UInt64](../sql_reference/data_types/int_uint.md#uint-ranges)) — Maximum [lifetime](../sql_reference/dictionaries/external_dictionaries/external_dicts_dict_lifetime.md) of the dictionary in memory, after which ClickHouse tries to reload the dictionary (if `invalidate_query` is set, then only if it has changed). Set in seconds.
+- `loading_start_time` ([DateTime](../sql_reference/data_types/datetime.md)) — Start time for loading the dictionary.
+- `last_successful_update_time` ([DateTime](../sql_reference/data_types/datetime.md)) — End time for loading or updating the dictionary. Helps to monitor some troubles with external sources and investigate causes.
+- `loading_duration` ([Float32](../sql_reference/data_types/float.md)) — Duration of a dictionary loading.
+- `last_exception` ([String](../sql_reference/data_types/string.md)) — Text of the error that occurs when creating or reloading the dictionary if the dictionary couldn't be created.
 
-Note that the amount of memory used by the dictionary is not proportional to the number of items stored in it. So for flat and cached dictionaries, all the memory cells are pre-assigned, regardless of how full the dictionary actually is.
+
+**Example**
+
+Configure the dictionary.
+
+```sql
+CREATE DICTIONARY dictdb.dict
+(
+    `key` Int64 DEFAULT -1,
+    `value_default` String DEFAULT 'world',
+    `value_expression` String DEFAULT 'xxx' EXPRESSION 'toString(127 * 172)'
+)
+PRIMARY KEY key
+SOURCE(CLICKHOUSE(HOST 'localhost' PORT 9000 USER 'default' TABLE 'dicttbl' DB 'dictdb'))
+LIFETIME(MIN 0 MAX 1)
+LAYOUT(FLAT())
+```
+
+Make sure that the dictionary is loaded.
+
+```sql
+SELECT * FROM system.dictionaries
+```
+
+```text
+┌─database─┬─name─┬─status─┬─origin──────┬─type─┬─key────┬─attribute.names──────────────────────┬─attribute.types─────┬─bytes_allocated─┬─query_count─┬─hit_rate─┬─element_count─┬───────────load_factor─┬─source─────────────────────┬─lifetime_min─┬─lifetime_max─┬──loading_start_time─┌──last_successful_update_time─┬──────loading_duration─┬─last_exception─┐
+│ dictdb   │ dict │ LOADED │ dictdb.dict │ Flat │ UInt64 │ ['value_default','value_expression'] │ ['String','String'] │           74032 │           0 │        1 │             1 │ 0.0004887585532746823 │ ClickHouse: dictdb.dicttbl │            0 │            1 │ 2020-03-04 04:17:34 │   2020-03-04 04:30:34        │                 0.002 │                │
+└──────────┴──────┴────────┴─────────────┴──────┴────────┴──────────────────────────────────────┴─────────────────────┴─────────────────┴─────────────┴──────────┴───────────────┴───────────────────────┴────────────────────────────┴──────────────┴──────────────┴─────────────────────┴──────────────────────────────┘───────────────────────┴────────────────┘
+```
 
 ## system.events {#system_tables-events}
 

docs/en/operations/troubleshooting.md

@@ -12,12 +12,12 @@ toc_title: Troubleshooting
 
 ## Installation {#troubleshooting-installation-errors}
 
-### You Cannot Get Deb Packages From Clickhouse Repository With Apt-get {#you-cannot-get-deb-packages-from-clickhouse-repository-with-apt-get}
+### You Cannot Get Deb Packages from ClickHouse Repository with Apt-get {#you-cannot-get-deb-packages-from-clickhouse-repository-with-apt-get}
 
 -   Check firewall settings.
 -   If you cannot access the repository for any reason, download packages as described in the [Getting started](../getting_started/index.md) article and install them manually using the `sudo dpkg -i <packages>` command. You will also need the `tzdata` package.
 
-## Connecting To the Server {#troubleshooting-accepts-no-connections}
+## Connecting to the Server {#troubleshooting-accepts-no-connections}
 
 Possible issues:
 
@@ -137,7 +137,7 @@ If you start `clickhouse-client` with the `stack-trace` parameter, ClickHouse re
 
 You might see a message about a broken connection. In this case, you can repeat the query. If the connection breaks every time you perform the query, check the server logs for errors.
 
-## Efficiency Of Query Processing {#troubleshooting-too-slow}
+## Efficiency of Query Processing {#troubleshooting-too-slow}
 
 If you see that ClickHouse is working too slowly, you need to profile the load on the server resources and network for your queries.
 

docs/en/sql_reference/dictionaries/external_dictionaries/external_dicts_dict_lifetime.md

@@ -49,6 +49,11 @@ or
 LIFETIME(MIN 300 MAX 360)
 ```
 
+If `<min>0</min>` and `<max>0</max>`, ClickHouse does not reload the dictionary by timeout. 
+In this case, ClickHouse can reload the dictionary earlier if the dictionary configuration file was changed or the `SYSTEM RELOAD DICTIONARY` command was executed.
+ 
+When upgrading the dictionaries, the ClickHouse server applies different logic depending on the type of [source](external_dicts_dict_sources.md):
+
 When upgrading the dictionaries, the ClickHouse server applies different logic depending on the type of [source](external_dicts_dict_sources.md):
 
 -   For a text file, it checks the time of modification. If the time differs from the previously recorded time, the dictionary is updated.

docs/en/sql_reference/dictionaries/external_dictionaries/external_dicts_dict_sources.md

@@ -488,7 +488,7 @@ SOURCE(MYSQL(
 ))
 ```
 
-### Clickhouse {#dicts-external_dicts_dict_sources-clickhouse}
+### ClickHouse {#dicts-external_dicts_dict_sources-clickhouse}
 
 Example of settings:
 

docs/en/sql_reference/operators.md

@@ -58,7 +58,7 @@ Groups of operators are listed in order of priority (the higher it is in the lis
 
 `a NOT BETWEEN b AND c` – The same as `a < b OR a > c`.
 
-## Operators For Working With Data Sets {#operators-for-working-with-data-sets}
+## Operators for Working with Data Sets {#operators-for-working-with-data-sets}
 
 *See [IN operators](statements/select.md#select-in-operators).*
 
@@ -70,7 +70,7 @@ Groups of operators are listed in order of priority (the higher it is in the lis
 
 `a GLOBAL NOT IN ...` – The `globalNotIn(a, b)` function.
 
-## Operators For Working With Dates and Times {#operators-datetime}
+## Operators for Working with Dates and Times {#operators-datetime}
 
 ### EXTRACT {#operator-extract}
 
@@ -231,7 +231,7 @@ Sometimes this doesn’t work the way you expect. For example, `SELECT 4 > 2 > 3
 
 For efficiency, the `and` and `or` functions accept any number of arguments. The corresponding chains of `AND` and `OR` operators are transformed to a single call of these functions.
 
-## Checking For `NULL` {#checking-for-null}
+## Checking for `NULL` {#checking-for-null}
 
 ClickHouse supports the `IS NULL` and `IS NOT NULL` operators.
 

docs/en/whats_new/changelog/2017.md

@@ -152,7 +152,7 @@ This release contains bug fixes for the previous release 1.1.54276:
 -   Fixed parsing when inserting in RowBinary format if input data starts with’;’.
 -   Errors during runtime compilation of certain aggregate functions (e.g. `groupArray()`).
 
-### Clickhouse Release 1.1.54276, 2017-08-16 {#clickhouse-release-1-1-54276-2017-08-16}
+### ClickHouse Release 1.1.54276, 2017-08-16 {#clickhouse-release-1-1-54276-2017-08-16}
 
 #### New features: {#new-features-4}
 

docs/en/whats_new/changelog/2018.md

@@ -839,7 +839,7 @@ toc_title: '2018'
 -   Restored the behavior for queries like `SELECT * FROM remote('server2', default.table) WHERE col IN (SELECT col2 FROM default.table)` when the right side of the `IN` should use a remote `default.table` instead of a local one. This behavior was broken in version 1.1.54358.
 -   Removed extraneous error-level logging of `Not found column ... in block`.
 
-### Clickhouse Release 1.1.54362, 2018-03-11 {#clickhouse-release-1-1-54362-2018-03-11}
+### ClickHouse Release 1.1.54362, 2018-03-11 {#clickhouse-release-1-1-54362-2018-03-11}
 
 #### New features: {#new-features-16}
 
@@ -929,13 +929,13 @@ toc_title: '2018'
 -   Removed the `strict_insert_defaults` setting. If you were using this functionality, write to `clickhouse-feedback@yandex-team.com`.
 -   Removed the `UnsortedMergeTree` engine.
 
-### Clickhouse Release 1.1.54343, 2018-02-05 {#clickhouse-release-1-1-54343-2018-02-05}
+### ClickHouse Release 1.1.54343, 2018-02-05 {#clickhouse-release-1-1-54343-2018-02-05}
 
 -   Added macros support for defining cluster names in distributed DDL queries and constructors of Distributed tables: `CREATE TABLE distr ON CLUSTER '{cluster}' (...) ENGINE = Distributed('{cluster}', 'db', 'table')`.
 -   Now queries like `SELECT ... FROM table WHERE expr IN (subquery)` are processed using the `table` index.
 -   Improved processing of duplicates when inserting to Replicated tables, so they no longer slow down execution of the replication queue.
 
-### Clickhouse Release 1.1.54342, 2018-01-22 {#clickhouse-release-1-1-54342-2018-01-22}
+### ClickHouse Release 1.1.54342, 2018-01-22 {#clickhouse-release-1-1-54342-2018-01-22}
 
 This release contains bug fixes for the previous release 1.1.54337:
 
@@ -947,7 +947,7 @@ This release contains bug fixes for the previous release 1.1.54337:
 -   Buffer tables now work correctly when MATERIALIZED columns are present in the destination table (by zhang2014).
 -   Fixed a bug in implementation of NULL.
 
-### Clickhouse Release 1.1.54337, 2018-01-18 {#clickhouse-release-1-1-54337-2018-01-18}
+### ClickHouse Release 1.1.54337, 2018-01-18 {#clickhouse-release-1-1-54337-2018-01-18}
 
 #### New features: {#new-features-17}
 

docs/en/whats_new/changelog/2019.md

@@ -128,11 +128,11 @@ toc_title: '2019'
 
 ## ClickHouse release v19.16 {#clickhouse-release-v19-16}
 
-#### Clickhouse release v19.16.14.65, 2020-03-25
+#### ClickHouse release v19.16.14.65, 2020-03-25
 
 * Fixed up a bug in batched calculations of ternary logical OPs on multiple arguments (more than 10). [#8718](https://github.com/ClickHouse/ClickHouse/pull/8718) ([Alexander Kazakov](https://github.com/Akazz)) This bugfix was backported to version 19.16 by a special request from Altinity.
 
-#### Clickhouse release v19.16.14.65, 2020-03-05 {#clickhouse-release-v19-16-14-65-2020-03-05}
+#### ClickHouse release v19.16.14.65, 2020-03-05 {#clickhouse-release-v19-16-14-65-2020-03-05}
 
 -   Fix distributed subqueries incompatibility with older CH versions. Fixes [\#7851](https://github.com/ClickHouse/ClickHouse/issues/7851)
     [(tabplubix)](https://github.com/tavplubix)
@@ -1865,7 +1865,7 @@ toc_title: '2019'
 -   Аdded tool for converting an old month-partitioned part to the custom-partitioned format. [\#4195](https://github.com/ClickHouse/ClickHouse/pull/4195) ([Alex Zatelepin](https://github.com/ztlpn))
 -   Added docs about two datasets in s3. [\#4144](https://github.com/ClickHouse/ClickHouse/pull/4144) ([alesapin](https://github.com/alesapin))
 -   Added script which creates changelog from pull requests description. [\#4169](https://github.com/ClickHouse/ClickHouse/pull/4169) [\#4173](https://github.com/ClickHouse/ClickHouse/pull/4173) ([KochetovNicolai](https://github.com/KochetovNicolai)) ([KochetovNicolai](https://github.com/KochetovNicolai))
--   Added puppet module for Clickhouse. [\#4182](https://github.com/ClickHouse/ClickHouse/pull/4182) ([Maxim Fedotov](https://github.com/MaxFedotov))
+-   Added puppet module for ClickHouse. [\#4182](https://github.com/ClickHouse/ClickHouse/pull/4182) ([Maxim Fedotov](https://github.com/MaxFedotov))
 -   Added docs for a group of undocumented functions. [\#4168](https://github.com/ClickHouse/ClickHouse/pull/4168) ([Winter Zhang](https://github.com/zhang2014))
 -   ARM build fixes. [\#4210](https://github.com/ClickHouse/ClickHouse/pull/4210)[\#4306](https://github.com/ClickHouse/ClickHouse/pull/4306) [\#4291](https://github.com/ClickHouse/ClickHouse/pull/4291) ([proller](https://github.com/proller)) ([proller](https://github.com/proller))
 -   Dictionary tests now able to run from `ctest`. [\#4189](https://github.com/ClickHouse/ClickHouse/pull/4189) ([proller](https://github.com/proller))

docs/en/whats_new/index.md

@@ -3,3 +3,4 @@ toc_folder_title: What's New
 toc_priority: 72
 ---
 
+

docs/es/development/tests.md

@@ -13,7 +13,7 @@ Las pruebas funcionales son las más simples y cómodas de usar. La mayoría de
 
 Cada prueba funcional envía una o varias consultas al servidor ClickHouse en ejecución y compara el resultado con la referencia.
 
-Las pruebas se encuentran en `testsies` directorio. Hay dos subdirectorios: `stateless` y `stateful`. Las pruebas sin estado ejecutan consultas sin datos de prueba precargados: a menudo crean pequeños conjuntos de datos sintéticos sobre la marcha, dentro de la prueba misma. Las pruebas estatales requieren datos de prueba precargados de Yandex.Métrica y no está disponible para el público en general. Tendemos a usar sólo `stateless` pruebas y evitar la adición de nuevos `stateful` prueba.
+Las pruebas se encuentran en `queries` directorio. Hay dos subdirectorios: `stateless` y `stateful`. Las pruebas sin estado ejecutan consultas sin datos de prueba precargados: a menudo crean pequeños conjuntos de datos sintéticos sobre la marcha, dentro de la prueba misma. Las pruebas estatales requieren datos de prueba precargados de Yandex.Métrica y no está disponible para el público en general. Tendemos a usar sólo `stateless` pruebas y evitar la adición de nuevos `stateful` prueba.
 
 Cada prueba puede ser de dos tipos: `.sql` y `.sh`. `.sql` test es el script SQL simple que se canaliza a `clickhouse-client --multiquery --testmode`. `.sh` test es un script que se ejecuta por sí mismo.
 
@@ -21,7 +21,7 @@ Para ejecutar todas las pruebas, use `testskhouse-test` herramienta. Mira `--hel
 
 La forma más sencilla de invocar pruebas funcionales es copiar `clickhouse-client` a `/usr/bin/`, ejecutar `clickhouse-server` y luego ejecutar `./clickhouse-test` de su propio directorio.
 
-Para agregar una nueva prueba, cree un `.sql` o `.sh` archivo en `testsies/0_stateless` directorio, compruébelo manualmente y luego genere `.reference` archivo de la siguiente manera: `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` o `./00000_test.sh > ./00000_test.reference`.
+Para agregar una nueva prueba, cree un `.sql` o `.sh` archivo en `queries/0_stateless` directorio, compruébelo manualmente y luego genere `.reference` archivo de la siguiente manera: `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` o `./00000_test.sh > ./00000_test.reference`.
 
 Las pruebas deben usar (crear, soltar, etc.) solo tablas en `test` base de datos que se supone que se crea de antemano; también las pruebas pueden usar tablas temporales.
 
@@ -36,7 +36,7 @@ deshabilitar estos grupos de pruebas utilizando `--no-zookeeper`, `--no-shard` y
 
 ## Bugs conocidos {#known-bugs}
 
-Si conocemos algunos errores que se pueden reproducir fácilmente mediante pruebas funcionales, colocamos pruebas funcionales preparadas en `testsies/bugs` directorio. Estas pruebas se moverán a `teststests_stateless` cuando se corrigen errores.
+Si conocemos algunos errores que se pueden reproducir fácilmente mediante pruebas funcionales, colocamos pruebas funcionales preparadas en `queries/bugs` directorio. Estas pruebas se moverán a `teststests_stateless` cuando se corrigen errores.
 
 ## Pruebas de integración {#integration-tests}
 

docs/fa/development/tests.md

@@ -14,7 +14,7 @@ toc_title: "\u0646\u062D\u0648\u0647 \u0627\u062C\u0631\u0627\u06CC \u062A\u0633
 
 هر تست عملکردی یک یا چند نمایش داده شد به سرور در حال اجرا تاتر می فرستد و نتیجه را با مرجع مقایسه می کند.
 
-تست ها در واقع `testsies` فهرست راهنما. دو زیرشاخه وجود دارد: `stateless` و `stateful`. تست های بدون تابعیت بدون هیچ گونه داده های تست پیش بارگذاری شده نمایش داده می شوند-اغلب مجموعه داده های مصنوعی کوچک را در پرواز در داخل تست خود ایجاد می کنند. تست های نفرت انگیز نیاز به داده های تست از قبل نصب شده از یاندکس.متریکا و در دسترس عموم نیست. ما تمایل به استفاده از تنها `stateless` تست ها و جلوگیری از اضافه کردن جدید `stateful` تستها
+تست ها در واقع `queries` فهرست راهنما. دو زیرشاخه وجود دارد: `stateless` و `stateful`. تست های بدون تابعیت بدون هیچ گونه داده های تست پیش بارگذاری شده نمایش داده می شوند-اغلب مجموعه داده های مصنوعی کوچک را در پرواز در داخل تست خود ایجاد می کنند. تست های نفرت انگیز نیاز به داده های تست از قبل نصب شده از یاندکس.متریکا و در دسترس عموم نیست. ما تمایل به استفاده از تنها `stateless` تست ها و جلوگیری از اضافه کردن جدید `stateful` تستها
 
 هر تست می تواند یکی از دو نوع باشد: `.sql` و `.sh`. `.sql` تست اسکریپت ساده مربع است که به لوله کشی است `clickhouse-client --multiquery --testmode`. `.sh` تست یک اسکریپت است که به خودی خود اجرا است.
 
@@ -22,7 +22,7 @@ toc_title: "\u0646\u062D\u0648\u0647 \u0627\u062C\u0631\u0627\u06CC \u062A\u0633
 
 ساده ترین راه برای فراخوانی تست های کاربردی کپی است `clickhouse-client` به `/usr/bin/` فرار کن `clickhouse-server` و سپس اجرا کنید `./clickhouse-test` از دایرکتوری خود را.
 
-برای اضافه کردن تست جدید, ایجاد یک `.sql` یا `.sh` پرونده در `testsies/0_stateless` فهرست راهنما را به صورت دستی بررسی کنید و سپس تولید کنید `.reference` پرونده به روش زیر: `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` یا `./00000_test.sh > ./00000_test.reference`.
+برای اضافه کردن تست جدید, ایجاد یک `.sql` یا `.sh` پرونده در `queries/0_stateless` فهرست راهنما را به صورت دستی بررسی کنید و سپس تولید کنید `.reference` پرونده به روش زیر: `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` یا `./00000_test.sh > ./00000_test.reference`.
 
 تست باید استفاده کنید (ساختن, قطره, و غیره) تنها جداول در `test` پایگاه داده است که فرض بر این است که از قبل ایجاد می شود; همچنین تست می توانید جداول موقت استفاده.
 
@@ -37,7 +37,7 @@ toc_title: "\u0646\u062D\u0648\u0647 \u0627\u062C\u0631\u0627\u06CC \u062A\u0633
 
 ## اشکالات شناخته شده {#known-bugs}
 
-اگر ما می دانیم برخی از اشکالات است که می تواند به راحتی توسط تست های کاربردی تکثیر, ما تست های عملکردی تهیه شده در `testsies/bugs` فهرست راهنما. این تست خواهد شد به نقل مکان کرد `teststests_stateless` هنگامی که اشکالات ثابت هستند.
+اگر ما می دانیم برخی از اشکالات است که می تواند به راحتی توسط تست های کاربردی تکثیر, ما تست های عملکردی تهیه شده در `queries/bugs` فهرست راهنما. این تست خواهد شد به نقل مکان کرد `teststests_stateless` هنگامی که اشکالات ثابت هستند.
 
 ## تست های ادغام {#integration-tests}
 

docs/fr/development/tests.md

@@ -13,7 +13,7 @@ Les tests fonctionnels sont les plus simples et pratiques à utiliser. La plupar
 
 Chaque test fonctionnel envoie une ou plusieurs requêtes au serveur clickhouse en cours d'exécution et compare le résultat avec la référence.
 
-Les Tests sont situés dans `testsies` répertoire. Il y a deux sous-répertoires: `stateless` et `stateful`. Les tests sans état exécutent des requêtes sans données de test préchargées - ils créent souvent de petits ensembles de données synthétiques à la volée, dans le test lui-même. Les tests avec État nécessitent des données de test préchargées de Yandex.Metrica et non disponible pour le grand public. Nous avons tendance à utiliser uniquement `stateless` tests et éviter d'ajouter de nouveaux `stateful` test.
+Les Tests sont situés dans `queries` répertoire. Il y a deux sous-répertoires: `stateless` et `stateful`. Les tests sans état exécutent des requêtes sans données de test préchargées - ils créent souvent de petits ensembles de données synthétiques à la volée, dans le test lui-même. Les tests avec État nécessitent des données de test préchargées de Yandex.Metrica et non disponible pour le grand public. Nous avons tendance à utiliser uniquement `stateless` tests et éviter d'ajouter de nouveaux `stateful` test.
 
 Chaque test peut être de deux types: `.sql` et `.sh`. `.sql` test est le script SQL simple qui est canalisé vers `clickhouse-client --multiquery --testmode`. `.sh` test est un script qui est exécuté par lui-même.
 
@@ -21,7 +21,7 @@ Pour exécuter tous les tests, utilisez `testskhouse-test` outil. Regarder `--he
 
 Le moyen le plus simple d'invoquer des tests fonctionnels est de copier `clickhouse-client` de `/usr/bin/`, exécuter `clickhouse-server` et puis exécutez `./clickhouse-test` à partir de son propre répertoire.
 
-Pour ajouter un nouveau test, créez un `.sql` ou `.sh` fichier dans `testsies/0_stateless` répertoire, vérifiez-le manuellement, puis générez `.reference` fichier de la façon suivante: `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` ou `./00000_test.sh > ./00000_test.reference`.
+Pour ajouter un nouveau test, créez un `.sql` ou `.sh` fichier dans `queries/0_stateless` répertoire, vérifiez-le manuellement, puis générez `.reference` fichier de la façon suivante: `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` ou `./00000_test.sh > ./00000_test.reference`.
 
 Les Tests doivent utiliser (create, drop, etc) uniquement des tables dans `test` base de données supposée être créée au préalable; les tests peuvent également utiliser des tables temporaires.
 
@@ -36,7 +36,7 @@ désactivez ces groupes de tests en utilisant `--no-zookeeper`, `--no-shard` et
 
 ## Bugs connus {#known-bugs}
 
-Si nous connaissons des bugs qui peuvent être facilement reproduits par des tests fonctionnels, nous plaçons des tests fonctionnels préparés dans `testsies/bugs` répertoire. Ces tests seront déplacés à `teststests_stateless` quand les bugs sont corrigés.
+Si nous connaissons des bugs qui peuvent être facilement reproduits par des tests fonctionnels, nous plaçons des tests fonctionnels préparés dans `queries/bugs` répertoire. Ces tests seront déplacés à `teststests_stateless` quand les bugs sont corrigés.
 
 ## Les Tests D'Intégration {#integration-tests}
 

docs/ja/development/tests.md

@@ -13,7 +13,7 @@ toc_title: "ClickHouse\u30C6\u30B9\u30C8\u3092\u5B9F\u884C\u3059\u308B\u65B9\u6C
 
 各機能テストは、実行中のclickhouseサーバーに一つまたは複数のクエリを送信し、参照と結果を比較します。
 
-テストは `testsies` ディレクトリ。 つのサブディレクトリがあります: `stateless` と `stateful`. ステートレステストでは、プリロードされたテストデータを使用せずにクエリを実行します。 ステートフルテストでは、Yandexのテストデータが必要です。メトリカと一般市民には利用できません。 我々は唯一の使用する傾向があります `stateless` テストと新しい追加を避ける `stateful` テスト
+テストは `queries` ディレクトリ。 つのサブディレクトリがあります: `stateless` と `stateful`. ステートレステストでは、プリロードされたテストデータを使用せずにクエリを実行します。 ステートフルテストでは、Yandexのテストデータが必要です。メトリカと一般市民には利用できません。 我々は唯一の使用する傾向があります `stateless` テストと新しい追加を避ける `stateful` テスト
 
 それぞれの試験できるの種類: `.sql` と `.sh`. `.sql` testは、パイプ処理される単純なSQLスクリプトです `clickhouse-client --multiquery --testmode`. `.sh` テストは、単独で実行されるスクリプトです。
 
@@ -21,7 +21,7 @@ toc_title: "ClickHouse\u30C6\u30B9\u30C8\u3092\u5B9F\u884C\u3059\u308B\u65B9\u6C
 
 機能テストを呼び出す最も簡単な方法は、コピーすることです `clickhouse-client` に `/usr/bin/`、実行 `clickhouse-server` そして、実行 `./clickhouse-test` 独自のディレクトリから。
 
-新しいテストを追加するには、 `.sql` または `.sh` ファイル `testsies/0_stateless` ディレクトリは、手動でチェックしてから生成 `.reference` 次の方法でファイル: `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` または `./00000_test.sh > ./00000_test.reference`.
+新しいテストを追加するには、 `.sql` または `.sh` ファイル `queries/0_stateless` ディレクトリは、手動でチェックしてから生成 `.reference` 次の方法でファイル: `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` または `./00000_test.sh > ./00000_test.reference`.
 
 テストでは、（create、dropなど）テーブルのみを使用する必要があります `test` テストでは一時テーブルを使用することもできます。
 
@@ -36,7 +36,7 @@ toc_title: "ClickHouse\u30C6\u30B9\u30C8\u3092\u5B9F\u884C\u3059\u308B\u65B9\u6C
 
 ## 既知のバグ {#known-bugs}
 
-機能テストで簡単に再現できるいくつかのバグを知っていれば、準備された機能テストを `testsies/bugs` ディレクトリ。 これらのテストはに移動されます `teststests_stateless` バグが修正されたとき。
+機能テストで簡単に再現できるいくつかのバグを知っていれば、準備された機能テストを `queries/bugs` ディレクトリ。 これらのテストはに移動されます `teststests_stateless` バグが修正されたとき。
 
 ## 統合テスト {#integration-tests}
 

docs/ru/database_engines/mysql.md

@@ -6,8 +6,6 @@
 
 Не поддерживаемые виды запросов:
 
--   `ATTACH`/`DETACH`
--   `DROP`
 -   `RENAME`
 -   `CREATE TABLE`
 -   `ALTER`
@@ -16,7 +14,7 @@
 
 ``` sql
 CREATE DATABASE [IF NOT EXISTS] db_name [ON CLUSTER cluster]
-ENGINE = MySQL('host:port', 'database', 'user', 'password')
+ENGINE = MySQL('host:port', ['database' | database], 'user', 'password')
 ```
 
 **Параметры движка**

docs/ru/development/tests.md

@@ -10,7 +10,7 @@ Functional tests are the most simple and convenient to use. Most of ClickHouse f
 
 Each functional test sends one or multiple queries to the running ClickHouse server and compares the result with reference.
 
-Tests are located in `testsies` directory. There are two subdirectories: `stateless` and `stateful`. Stateless tests run queries without any preloaded test data - they often create small synthetic datasets on the fly, within the test itself. Stateful tests require preloaded test data from Yandex.Metrica and not available to general public. We tend to use only `stateless` tests and avoid adding new `stateful` tests.
+Tests are located in `queries` directory. There are two subdirectories: `stateless` and `stateful`. Stateless tests run queries without any preloaded test data - they often create small synthetic datasets on the fly, within the test itself. Stateful tests require preloaded test data from Yandex.Metrica and not available to general public. We tend to use only `stateless` tests and avoid adding new `stateful` tests.
 
 Each test can be one of two types: `.sql` and `.sh`. `.sql` test is the simple SQL script that is piped to `clickhouse-client --multiquery --testmode`. `.sh` test is a script that is run by itself.
 
@@ -18,7 +18,7 @@ To run all tests, use `testskhouse-test` tool. Look `--help` for the list of pos
 
 The most simple way to invoke functional tests is to copy `clickhouse-client` to `/usr/bin/`, run `clickhouse-server` and then run `./clickhouse-test` from its own directory.
 
-To add new test, create a `.sql` or `.sh` file in `testsies/0_stateless` directory, check it manually and then generate `.reference` file in the following way: `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` or `./00000_test.sh > ./00000_test.reference`.
+To add new test, create a `.sql` or `.sh` file in `queries/0_stateless` directory, check it manually and then generate `.reference` file in the following way: `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` or `./00000_test.sh > ./00000_test.reference`.
 
 Tests should use (create, drop, etc) only tables in `test` database that is assumed to be created beforehand; also tests can use temporary tables.
 
@@ -33,7 +33,7 @@ disable these groups of tests using `--no-zookeeper`, `--no-shard` and
 
 ## Known bugs {#known-bugs}
 
-If we know some bugs that can be easily reproduced by functional tests, we place prepared functional tests in `testsies/bugs` directory. These tests will be moved to `teststests_stateless` when bugs are fixed.
+If we know some bugs that can be easily reproduced by functional tests, we place prepared functional tests in `queries/bugs` directory. These tests will be moved to `teststests_stateless` when bugs are fixed.
 
 ## Integration Tests {#integration-tests}
 

docs/ru/operations/system_tables.md

@@ -135,27 +135,66 @@ SELECT * FROM system.contributors WHERE name='Olga Khvostikova'
 Такие куски могут быть присоединены с помощью [ALTER TABLE ATTACH PARTITION\|PART](../query_language/query_language/alter/#alter_attach-partition). Остальные столбцы описаны в [system.parts](#system_tables-parts).
 Если имя куска некорректно, значения некоторых столбцов могут быть `NULL`. Такие куски могут быть удалены с помощью [ALTER TABLE DROP DETACHED PART](../query_language/query_language/alter/#alter_drop-detached).
 
-## system.dictionaries {#system-dictionaries}
+## system.dictionaries {#system_tables-dictionaries}
 
-Содержит информацию о внешних словарях.
+Содержит информацию о [внешних словарях](../query_language/dicts/external_dicts.md).
 
 Столбцы:
 
--   `name String` — Имя словаря.
--   `type String` — Тип словаря: Flat, Hashed, Cache.
--   `origin String` — Путь к конфигурационному файлу, в котором описан словарь.
--   `attribute.names Array(String)` — Массив имён атрибутов, предоставляемых словарём.
--   `attribute.types Array(String)` — Соответствующий массив типов атрибутов, предоставляемых словарём.
--   `has_hierarchy UInt8` — Является ли словарь иерархическим.
--   `bytes_allocated UInt64` — Количество оперативной памяти, которое использует словарь.
--   `hit_rate Float64` — Для cache-словарей - доля использований, для которых значение было в кэше.
--   `element_count UInt64` — Количество хранящихся в словаре элементов.
--   `load_factor Float64` — Доля заполненности словаря (для hashed словаря - доля заполнения хэш-таблицы).
--   `creation_time DateTime` — Время создания или последней успешной перезагрузки словаря.
--   `last_exception String` — Текст ошибки, возникшей при создании или перезагрузке словаря, если словарь не удалось создать.
--   `source String` - Текст, описывающий источник данных для словаря.
+- `database` ([String](../data_types/string.md)) — Имя базы данных, в которой находится словарь, созданный с помощью DDL-запроса. Пустая строка для других словарей.
+- `name` ([String](../data_types/string.md)) — [Имя словаря](../query_language/dicts/external_dicts_dict.md).
+- `status` ([Enum8](../data_types/enum.md)) — Статус словаря. Возможные значения:
+     - `NOT_LOADED` — Словарь не загружен, потому что не использовался.
+     - `LOADED` — Словарь загружен успешно.
+     - `FAILED` — Словарь не загружен в результате ошибки.
+     - `LOADING` — Словарь в процессе загрузки.
+     - `LOADED_AND_RELOADING` — Словарь загружен успешно, сейчас перезагружается (частые причины: запрос [SYSTEM RELOAD DICTIONARY](../query_language/system.md#query_language-system-reload-dictionary), таймаут, изменение настроек словаря).
+     - `FAILED_AND_RELOADING` — Словарь не загружен в результате ошибки, сейчас перезагружается.
+- `origin` ([String](../data_types/string.md)) — Путь к конфигурационному файлу, описывающему словарь.
+- `type`  ([String](../data_types/string.md)) — Тип размещения словаря. [Хранение словарей в памяти](../query_language/dicts/external_dicts_dict_layout.md).
+- `key` — [Тип ключа](../query_language/dicts/external_dicts_dict_structure.md#ext_dict_structure-key): Числовой ключ ([UInt64](../data_types/int_uint.md#uint-ranges)) или Составной ключ ([String](../data_types/string.md)) — строка вида "(тип 1, тип 2, ..., тип n)".
+- `attribute.names` ([Array](../data_types/array.md)([String](../data_types/string.md))) — Массив [имен атрибутов](../query_language/dicts/external_dicts_dict_structure.md#ext_dict_structure-attributes), предоставляемых справочником.
+- `attribute.types` ([Array](../data_types/array.md)([String](../data_types/string.md))) — Соответствующий массив [типов атрибутов](../query_language/dicts/external_dicts_dict_structure.md#ext_dict_structure-attributes), предоставляемых справочником.
+- `bytes_allocated` ([UInt64](../data_types/int_uint.md#uint-ranges)) — Объем оперативной памяти, используемый словарем.
+- `query_count` ([UInt64](../data_types/int_uint.md#uint-ranges)) — Количество запросов с момента загрузки словаря или с момента последней успешной перезагрузки.
+- `hit_rate` ([Float64](../data_types/float.md)) — Для cache-словарей — процент закэшированных значений.
+- `element_count` ([UInt64](../data_types/int_uint.md#uint-ranges))  — Количество элементов, хранящихся в словаре.
+- `load_factor` ([Float64](../data_types/float.md)) — Процент заполнения словаря (для хэшированного словаря  — процент заполнения хэш-таблицы).
+- `source` ([String](../data_types/string.md)) — Текст, описывающий [источник данных](../query_language/dicts/external_dicts_dict_sources.md) для словаря.
+- `lifetime_min` ([UInt64](../data_types/int_uint.md#uint-ranges)) — Минимальное [время обновления](../query_language/dicts/external_dicts_dict_lifetime.md) словаря в памяти, по истечении которого Clickhouse попытается перезагрузить словарь (если задано `invalidate_query`, то только если он изменился). Задается в секундах. 
+- `lifetime_max` ([UInt64](../data_types/int_uint.md#uint-ranges)) — Максимальное [время обновления](../query_language/dicts/external_dicts_dict_lifetime.md) словаря в памяти, по истечении которого Clickhouse попытается перезагрузить словарь (если задано `invalidate_query`, то только если он изменился). Задается в секундах.
+- `loading_start_time` ([DateTime](../data_types/datetime.md)) — Время начала загрузки словаря.
+- `loading_duration` ([Float32](../data_types/float.md)) — Время, затраченное на загрузку словаря.
+- `last_exception` ([String](../data_types/string.md)) — Текст ошибки, возникающей при создании или перезагрузке словаря, если словарь не удалось создать.
 
-Заметим, что количество оперативной памяти, которое использует словарь, не является пропорциональным количеству элементов, хранящихся в словаре. Так, для flat и cached словарей, все ячейки памяти выделяются заранее, независимо от реальной заполненности словаря.
+**Пример**
+
+Настройте словарь.
+
+```sql
+CREATE DICTIONARY dictdb.dict
+(
+    `key` Int64 DEFAULT -1,
+    `value_default` String DEFAULT 'world',
+    `value_expression` String DEFAULT 'xxx' EXPRESSION 'toString(127 * 172)'
+)
+PRIMARY KEY key
+SOURCE(CLICKHOUSE(HOST 'localhost' PORT 9000 USER 'default' TABLE 'dicttbl' DB 'dictdb'))
+LIFETIME(MIN 0 MAX 1)
+LAYOUT(FLAT())
+```
+
+Убедитесь, что словарь загружен.
+
+```sql
+SELECT * FROM system.dictionaries
+```
+
+```text
+┌─database─┬─name─┬─status─┬─origin──────┬─type─┬─key────┬─attribute.names──────────────────────┬─attribute.types─────┬─bytes_allocated─┬─query_count─┬─hit_rate─┬─element_count─┬───────────load_factor─┬─source─────────────────────┬─lifetime_min─┬─lifetime_max─┬──loading_start_time─┌──last_successful_update_time─┬──────loading_duration─┬─last_exception─┐
+│ dictdb   │ dict │ LOADED │ dictdb.dict │ Flat │ UInt64 │ ['value_default','value_expression'] │ ['String','String'] │           74032 │           0 │        1 │             1 │ 0.0004887585532746823 │ ClickHouse: dictdb.dicttbl │            0 │            1 │ 2020-03-04 04:17:34 │   2020-03-04 04:30:34        │                 0.002 │                │
+└──────────┴──────┴────────┴─────────────┴──────┴────────┴──────────────────────────────────────┴─────────────────────┴─────────────────┴─────────────┴──────────┴───────────────┴───────────────────────┴────────────────────────────┴──────────────┴──────────────┴─────────────────────┴──────────────────────────────┘───────────────────────┴────────────────┘
+```
 
 ## system.events {#system_tables-events}
 

docs/ru/operations/table_engines/mergetree.md

@@ -494,14 +494,14 @@ ALTER TABLE example_table
 <storage_configuration>
     <disks>
         <disk_name_1> <!-- disk name -->
-            <path>/mnt/fast_ssd/clickhouse</path>
+            <path>/mnt/fast_ssd/clickhouse/</path>
         </disk_name_1>
         <disk_name_2>
-            <path>/mnt/hdd1/clickhouse</path>
+            <path>/mnt/hdd1/clickhouse/</path>
             <keep_free_space_bytes>10485760</keep_free_space_bytes>
         </disk_name_2>
         <disk_name_3>
-            <path>/mnt/hdd2/clickhouse</path>
+            <path>/mnt/hdd2/clickhouse/</path>
             <keep_free_space_bytes>10485760</keep_free_space_bytes>
         </disk_name_3>
 

docs/toc_zh.yml

@@ -1,251 +0,0 @@
-nav:
-
-- '介绍':
-  - '概貌': 'index.md'
-  - 'ClickHouse的独特功能': 'introduction/distinctive_features.md'
-  - 'ClickHouse功能可被视为缺点': 'introduction/features_considered_disadvantages.md'
-  - '性能': 'introduction/performance.md'
-  - '历史': 'introduction/history.md'
-  - '使用者': 'introduction/adopters.md'
-
-- '入门指南':
-  - 'hidden': 'getting_started/index.md'
-  - '安装': 'getting_started/install.md'
-  - '教程': 'getting_started/tutorial.md'
-  - '示例数据集':
-    - '介绍': 'getting_started/example_datasets/index.md'
-    - '航班飞行数据': 'getting_started/example_datasets/ontime.md'
-    - '纽约市出租车数据': 'getting_started/example_datasets/nyc_taxi.md'
-    - 'AMPLab大数据基准测试': 'getting_started/example_datasets/amplab_benchmark.md'
-    - '维基访问数据': 'getting_started/example_datasets/wikistat.md'
-    - 'Criteo TB级别点击日志': 'getting_started/example_datasets/criteo.md'
-    - 'Star Schema基准测试': 'getting_started/example_datasets/star_schema.md'
-    - 'Yandex.Metrica': 'getting_started/example_datasets/metrica.md'
-  - 'Playground': 'getting_started/playground.md'
-
-- '客户端':
-  - '介绍': 'interfaces/index.md'
-  - '命令行客户端接口': 'interfaces/cli.md'
-  - '原生客户端接口 (TCP)': 'interfaces/tcp.md'
-  - 'HTTP 客户端接口': 'interfaces/http.md'
-  - 'MySQL 客户端接口': 'interfaces/mysql.md'
-  - '输入输出格式': 'interfaces/formats.md'
-  - 'JDBC 驱动': 'interfaces/jdbc.md'
-  - 'ODBC 驱动': 'interfaces/odbc.md'
-  - 'C ++客户端库': 'interfaces/cpp.md'
-  - '第三方':
-    - '客户端库': 'interfaces/third-party/client_libraries.md'
-    - '集成': 'interfaces/third-party/integrations.md'
-    - '可视界面': 'interfaces/third-party/gui.md'
-    - '代理': 'interfaces/third-party/proxy.md'
-
-- '数据类型':
-  - '介绍': 'data_types/index.md'
-  - 'UInt8, UInt16, UInt32, UInt64, Int8, Int16, Int32, Int64': 'data_types/int_uint.md'
-  - 'Float32, Float64': 'data_types/float.md'
-  - 'Decimal': 'data_types/decimal.md'
-  - 'Boolean values': 'data_types/boolean.md'
-  - 'String': 'data_types/string.md'
-  - 'FixedString(N)': 'data_types/fixedstring.md'
-  - 'UUID': 'data_types/uuid.md'
-  - 'Date': 'data_types/date.md'
-  - 'DateTime64': 'data_types/datetime64.md'
-  - 'DateTime': 'data_types/datetime.md'
-  - 'Enum': 'data_types/enum.md'
-  - 'Array(T)': 'data_types/array.md'
-  - 'AggregateFunction(name, types_of_arguments...)': 'data_types/nested_data_structures/aggregatefunction.md'
-  - 'Tuple(T1, T2, ...)': 'data_types/tuple.md'
-  - 'Nullable': 'data_types/nullable.md'
-  - '嵌套数据结构':
-    - 'hidden': 'data_types/nested_data_structures/index.md'
-    - 'Nested(Name1 Type1, Name2 Type2, ...)': 'data_types/nested_data_structures/nested.md'
-  - '特殊数据类型':
-    - 'hidden': 'data_types/special_data_types/index.md'
-    - 'Expression': 'data_types/special_data_types/expression.md'
-    - 'Set': 'data_types/special_data_types/set.md'
-    - 'Nothing': 'data_types/special_data_types/nothing.md'
-    - 'Interval': 'data_types/special_data_types/interval.md'
-  - 'Domain类型':
-    - '介绍': 'data_types/domains/overview.md'
-    - 'IPv4': 'data_types/domains/ipv4.md'
-    - 'IPv6': 'data_types/domains/ipv6.md'
-
-- '数据库引擎':
-    - '介绍': 'database_engines/index.md'
-    - 'MySQL': 'database_engines/mysql.md'
-    - 'Lazy': 'database_engines/lazy.md'
-
-- '表引擎':
-  - '介绍': 'operations/table_engines/index.md'
-  - 'MergeTree':
-    - 'MergeTree': 'operations/table_engines/mergetree.md'
-    - 'Data Replication': 'operations/table_engines/replication.md'
-    - 'Custom Partitioning Key': 'operations/table_engines/custom_partitioning_key.md'
-    - 'ReplacingMergeTree': 'operations/table_engines/replacingmergetree.md'
-    - 'SummingMergeTree': 'operations/table_engines/summingmergetree.md'
-    - 'AggregatingMergeTree': 'operations/table_engines/aggregatingmergetree.md'
-    - 'CollapsingMergeTree': 'operations/table_engines/collapsingmergetree.md'
-    - 'VersionedCollapsingMergeTree': 'operations/table_engines/versionedcollapsingmergetree.md'
-    - 'GraphiteMergeTree': 'operations/table_engines/graphitemergetree.md'
-  - 'Log':
-    - '介绍': 'operations/table_engines/log_family.md'
-    - 'StripeLog': 'operations/table_engines/stripelog.md'
-    - 'Log': 'operations/table_engines/log.md'
-    - 'TinyLog': 'operations/table_engines/tinylog.md'
-  - '外部表引擎':
-    - 'Kafka': 'operations/table_engines/kafka.md'
-    - 'MySQL': 'operations/table_engines/mysql.md'
-    - 'JDBC': 'operations/table_engines/jdbc.md'
-    - 'ODBC': 'operations/table_engines/odbc.md'
-    - 'HDFS': 'operations/table_engines/hdfs.md'
-  - '其他表引擎':
-    - 'Distributed': 'operations/table_engines/distributed.md'
-    - 'External data': 'operations/table_engines/external_data.md'
-    - 'Dictionary': 'operations/table_engines/dictionary.md'
-    - 'Merge': 'operations/table_engines/merge.md'
-    - 'File': 'operations/table_engines/file.md'
-    - 'Null': 'operations/table_engines/null.md'
-    - 'Set': 'operations/table_engines/set.md'
-    - 'Join': 'operations/table_engines/join.md'
-    - 'URL': 'operations/table_engines/url.md'
-    - 'View': 'operations/table_engines/view.md'
-    - 'MaterializedView': 'operations/table_engines/materializedview.md'
-    - 'Memory': 'operations/table_engines/memory.md'
-    - 'Buffer': 'operations/table_engines/buffer.md'
-    - 'GenerateRandom': 'operations/table_engines/generate.md'
-
-- 'SQL语法':
-  - 'hidden': 'query_language/index.md'
-  - 'SELECT': 'query_language/select.md'
-  - 'INSERT INTO': 'query_language/insert_into.md'
-  - 'CREATE': 'query_language/create.md'
-  - 'ALTER': 'query_language/alter.md'
-  - 'SYSTEM': 'query_language/system.md'
-  - 'SHOW': 'query_language/show.md'
-  - '其他类型的查询': 'query_language/misc.md'
-  - '函数':
-    - '介绍': 'query_language/functions/index.md'
-    - '算术函数': 'query_language/functions/arithmetic_functions.md'
-    - '比较函数': 'query_language/functions/comparison_functions.md'
-    - '逻辑函数': 'query_language/functions/logical_functions.md'
-    - '类型转换函数': 'query_language/functions/type_conversion_functions.md'
-    - '时间日期函数': 'query_language/functions/date_time_functions.md'
-    - '字符串函数': 'query_language/functions/string_functions.md'
-    - '字符串搜索函数': 'query_language/functions/string_search_functions.md'
-    - '字符串替换函数': 'query_language/functions/string_replace_functions.md'
-    - '条件函数 ': 'query_language/functions/conditional_functions.md'
-    - '数学函数': 'query_language/functions/math_functions.md'
-    - '取整函数': 'query_language/functions/rounding_functions.md'
-    - '数组函数': 'query_language/functions/array_functions.md'
-    - '字符串拆分合并函数': 'query_language/functions/splitting_merging_functions.md'
-    - '位操作函数': 'query_language/functions/bit_functions.md'
-    - '位图函数': 'query_language/functions/bitmap_functions.md'
-    - 'Hash函数': 'query_language/functions/hash_functions.md'
-    - '随机函数': 'query_language/functions/random_functions.md'
-    - '编码函数': 'query_language/functions/encoding_functions.md'
-    - 'UUID函数': 'query_language/functions/uuid_functions.md'
-    - 'URL函数': 'query_language/functions/url_functions.md'
-    - 'IP函数': 'query_language/functions/ip_address_functions.md'
-    - 'JSON函数': 'query_language/functions/json_functions.md'
-    - '高阶函数': 'query_language/functions/higher_order_functions.md'
-    - '字典函数': 'query_language/functions/ext_dict_functions.md'
-    - 'Yandex.Metrica字典函数': 'query_language/functions/ym_dict_functions.md'
-    - 'IN运算符相关函数': 'query_language/functions/in_functions.md'
-    - 'arrayJoin函数': 'query_language/functions/array_join.md'
-    - 'GEO函数': 'query_language/functions/geo.md'
-    - 'Nullable处理函数': 'query_language/functions/functions_for_nulls.md'
-    - '机器学习函数': 'query_language/functions/machine_learning_functions.md'
-    - 'Introspection': 'query_language/functions/introspection.md'
-    - '其他函数': 'query_language/functions/other_functions.md'
-  - '聚合函数':
-    - '介绍': 'query_language/agg_functions/index.md'
-    - '函数列表': 'query_language/agg_functions/reference.md'
-    - '聚合函数组合子': 'query_language/agg_functions/combinators.md'
-    - '参数化聚合函数': 'query_language/agg_functions/parametric_functions.md'
-  - '表引擎函数':
-    - '介绍': 'query_language/table_functions/index.md'
-    - 'file': 'query_language/table_functions/file.md'
-    - 'merge': 'query_language/table_functions/merge.md'
-    - 'numbers': 'query_language/table_functions/numbers.md'
-    - 'remote': 'query_language/table_functions/remote.md'
-    - 'url': 'query_language/table_functions/url.md'
-    - 'mysql': 'query_language/table_functions/mysql.md'
-    - 'jdbc': 'query_language/table_functions/jdbc.md'
-    - 'odbc': 'query_language/table_functions/odbc.md'
-    - 'hdfs': 'query_language/table_functions/hdfs.md'
-    - 'input': 'query_language/table_functions/input.md'
-    - 'generateRandom': 'query_language/table_functions/generate.md'
-  - '字典':
-    - '介绍': 'query_language/dicts/index.md'
-    - '外部字典':
-      - '介绍': 'query_language/dicts/external_dicts.md'
-      - '配置外部字典': 'query_language/dicts/external_dicts_dict.md'
-      - '字典的内存布局': 'query_language/dicts/external_dicts_dict_layout.md'
-      - '字典的刷新策略': 'query_language/dicts/external_dicts_dict_lifetime.md'
-      - '字典的外部数据源': 'query_language/dicts/external_dicts_dict_sources.md'
-      - '字典的键和字段值': 'query_language/dicts/external_dicts_dict_structure.md'
-      - 'Hierarchical dictionaries': 'query_language/dicts/external_dicts_dict_hierarchical.md'
-    - '内部字典': 'query_language/dicts/internal_dicts.md'
-  - '操作符': 'query_language/operators.md'
-  - '语法说明': 'query_language/syntax.md'
-
-- 'Guides':
-  - 'Overview': 'guides/index.md'
-  - 'Applying CatBoost Models': 'guides/apply_catboost_model.md'
-
-- '运维':
-  - '介绍': 'operations/index.md'
-  - '环境要求': 'operations/requirements.md'
-  - '监控': 'operations/monitoring.md'
-  - '故障排查': 'operations/troubleshooting.md'
-  - '使用建议': 'operations/tips.md'
-  - '版本升级': 'operations/update.md'
-  - '访问权限控制': 'operations/access_rights.md'
-  - '数据备份': 'operations/backup.md'
-  - '配置文件': 'operations/configuration_files.md'
-  - '配额': 'operations/quotas.md'
-  - '系统表': 'operations/system_tables.md'
-  - '优化性能':
-    - '查询分析': 'operations/performance/sampling_query_profiler.md'
-  - '测试硬件': 'operations/performance_test.md'
-  - 'Server参数配置':
-    - '介绍': 'operations/server_settings/index.md'
-    - 'Server参数说明': 'operations/server_settings/settings.md'
-  - 'Settings配置':
-    - '介绍': 'operations/settings/index.md'
-    - '查询权限管理': 'operations/settings/permissions_for_queries.md'
-    - '查询复杂性的限制': 'operations/settings/query_complexity.md'
-    - 'Setting列表': 'operations/settings/settings.md'
-    - 'Setting配置组': 'operations/settings/settings_profiles.md'
-    - '用户配置': 'operations/settings/settings_users.md'
-    - 'Settings的约束': 'operations/settings/constraints_on_settings.md'
-  - '常用工具':
-    - '介绍': 'operations/utils/index.md'
-    - 'clickhouse-copier': 'operations/utils/clickhouse-copier.md'
-    - 'clickhouse-local': 'operations/utils/clickhouse-local.md'
-    - 'clickhouse-benchmark': 'operations/utils/clickhouse-benchmark.md'
-
-- '常见问题':
-  - '一般的问题': 'faq/general.md'
-
-- '开发者指南':
-  - 'hidden': 'development/index.md'
-  - '开发者指南': 'development/developer_instruction.md'
-  - 'ClickHouse架构概述': 'development/architecture.md'
-  - 'ClickHouse Code Browser': 'development/browse_code.md'
-  - '如何在Linux中编译ClickHouse': 'development/build.md'
-  - '如何在Mac OS X中编译ClickHouse': 'development/build_osx.md'
-  - '如何在Linux中编译Mac OS X ClickHouse': 'development/build_cross_osx.md'
-  - '如何在Linux中编译AARCH64 (ARM64) ClickHouse': 'development/build_cross_arm.md'
-  - '如何编写C++代码': 'development/style.md'
-  - '如何运行ClickHouse测试': 'development/tests.md'
-  - '使用的第三方库': 'development/contrib.md'
-
-- '新功能特性':
-  - '路线图': 'roadmap.md'
-  - '更新日志':
-    - '2020': 'changelog/index.md'
-    - '2019': 'changelog/2019.md'
-    - '2018': 'changelog/2018.md'
-    - '2017': 'changelog/2017.md'
-  - '安全更改日志': 'security_changelog.md'

docs/tools/convert_toc.py

@@ -8,7 +8,7 @@ import yaml
 
 import util
 
-lang = 'ru'
+lang = 'zh'
 base_dir = os.path.join(os.path.dirname(__file__), '..')
 en_dir = os.path.join(base_dir, 'en')
 docs_dir = os.path.join(base_dir, lang)
@@ -57,7 +57,7 @@ def process_md_file(title, idx, original_path, proper_path):
     if original_path != proper_md_path:
         subprocess.check_call(f'git add {proper_md_path}', shell=True)
         if os.path.exists(original_path):
-            subprocess.check_call(f'git rm {original_path}', shell=True)
+            subprocess.check_call(f'rm {original_path}', shell=True)
 
 
 def process_toc_entry(entry, path, idx):
@@ -131,7 +131,7 @@ def sync_translation():
                     
                 util.write_md_file(lang_dst, en_meta, lang_content)
                 subprocess.check_call(f'git add {lang_dst}', shell=True)
-                subprocess.check_call(f'git rm {lang_src}', shell=True)
+                subprocess.check_call(f'rm {lang_src}', shell=True)
 
 
 if __name__ == '__main__':

docs/tools/nav.py

@@ -16,8 +16,8 @@ def build_nav_entry(root):
     if root.endswith('images'):
         return None, None, None
     result_items = []
-    index_meta, _ = util.read_md_file(os.path.join(root, 'index.md'))
-    current_title = index_meta.get('toc_folder_title', index_meta.get('toc_title', 'hidden'))
+    index_meta, index_content = util.read_md_file(os.path.join(root, 'index.md'))
+    current_title = index_meta.get('toc_folder_title', index_meta.get('toc_title', find_first_header(index_content)))
     for filename in os.listdir(root):
         path = os.path.join(root, filename)
         if os.path.isdir(path):
@@ -46,5 +46,7 @@ def build_nav(lang, args):
     _, _, nav = build_nav_entry(docs_dir)
     result = []
     for key, value in nav.items():
-        result.append({key: value})
+        if key and value:
+            result.append({key: value})
+    print('result', result)
     return result

docs/tools/translate/filter.py

@@ -36,7 +36,7 @@ def process_buffer(buffer, new_value, item=None, is_header=False):
         debug(f'Translate: "{text}" -> "{translated_text}"')
 
         if text and text[0].isupper() and not translated_text[0].isupper():
-            translated_text = translated_text.capitalize()
+            translated_text = translated_text[0].upper() + translated_text[1:]
 
         if text.startswith(' ') and not translated_text.startswith(' '):
             translated_text = ' ' + translated_text
@@ -47,12 +47,19 @@ def process_buffer(buffer, new_value, item=None, is_header=False):
         if is_header and translated_text.endswith('.'):
             translated_text = translated_text.rstrip('.')
 
-        title_case = False  # is_header and translate.default_target_language == 'en' and text[0].isupper()
-        title_case_whitelist = {'a', 'an', 'the', 'and', 'or'}
+        title_case = is_header and translate.default_target_language == 'en' and text[0].isupper()
+        title_case_whitelist = {
+            'a', 'an', 'the', 'and', 'or', 'that',
+            'of', 'on', 'for', 'from', 'with', 'to', 'in'
+        }
+        is_first_iteration = True
         for token in translated_text.split(' '):
-            if title_case and not token.isupper():
-                if token not in title_case_whitelist:
-                    token = token.capitalize()
+            if title_case and token.isascii() and not token.isupper():
+                if len(token) > 1 and token.lower() not in title_case_whitelist:
+                    token = token[0].upper() + token[1:]
+                elif not is_first_iteration:
+                    token = token.lower()
+            is_first_iteration = False
 
             new_value.append(pandocfilters.Str(token))
             new_value.append(pandocfilters.Space())

docs/tools/translate/remove_machine_translated_meta.py

@@ -0,0 +1,21 @@
+#!/usr/bin/env python3
+import os
+import sys
+sys.path.insert(0, os.path.join(os.path.dirname(__file__), '..'))
+import convert_toc
+import util
+
+
+if __name__ == '__main__':
+    path = sys.argv[1][2:]
+    convert_toc.init_redirects()
+    try:
+        path = convert_toc.redirects[path]
+    except KeyError:
+        pass
+    meta, content = util.read_md_file(path)
+    if 'machine_translated' in meta:
+        del meta['machine_translated']
+    if 'machine_translated_rev' in meta:
+        del meta['machine_translated_rev']
+    util.write_md_file(path, meta, content)

docs/zh/changelog/2017.md

@@ -1,265 +0,0 @@
----
-en_copy: true
----
-
-### ClickHouse release 1.1.54327, 2017-12-21 {#clickhouse-release-1-1-54327-2017-12-21}
-
-This release contains bug fixes for the previous release 1.1.54318:
-
--   Fixed bug with possible race condition in replication that could lead to data loss. This issue affects versions 1.1.54310 and 1.1.54318. If you use one of these versions with Replicated tables, the update is strongly recommended. This issue shows in logs in Warning messages like `Part ... from own log doesn't exist.` The issue is relevant even if you don’t see these messages in logs.
-
-### ClickHouse release 1.1.54318, 2017-11-30 {#clickhouse-release-1-1-54318-2017-11-30}
-
-This release contains bug fixes for the previous release 1.1.54310:
-
--   Fixed incorrect row deletions during merges in the SummingMergeTree engine
--   Fixed a memory leak in unreplicated MergeTree engines
--   Fixed performance degradation with frequent inserts in MergeTree engines
--   Fixed an issue that was causing the replication queue to stop running
--   Fixed rotation and archiving of server logs
-
-### ClickHouse release 1.1.54310, 2017-11-01 {#clickhouse-release-1-1-54310-2017-11-01}
-
-#### New features: {#new-features}
-
--   Custom partitioning key for the MergeTree family of table engines.
--   [Kafka](https://clickhouse.yandex/docs/en/operations/table_engines/kafka/) table engine.
--   Added support for loading [CatBoost](https://catboost.yandex/) models and applying them to data stored in ClickHouse.
--   Added support for time zones with non-integer offsets from UTC.
--   Added support for arithmetic operations with time intervals.
--   The range of values for the Date and DateTime types is extended to the year 2105.
--   Added the `CREATE MATERIALIZED VIEW x TO y` query (specifies an existing table for storing the data of a materialized view).
--   Added the `ATTACH TABLE` query without arguments.
--   The processing logic for Nested columns with names ending in -Map in a SummingMergeTree table was extracted to the sumMap aggregate function. You can now specify such columns explicitly.
--   Max size of the IP trie dictionary is increased to 128M entries.
--   Added the getSizeOfEnumType function.
--   Added the sumWithOverflow aggregate function.
--   Added support for the Cap’n Proto input format.
--   You can now customize compression level when using the zstd algorithm.
-
-#### Backward incompatible changes: {#backward-incompatible-changes}
-
--   Creation of temporary tables with an engine other than Memory is not allowed.
--   Explicit creation of tables with the View or MaterializedView engine is not allowed.
--   During table creation, a new check verifies that the sampling key expression is included in the primary key.
-
-#### Bug fixes: {#bug-fixes}
-
--   Fixed hangups when synchronously inserting into a Distributed table.
--   Fixed nonatomic adding and removing of parts in Replicated tables.
--   Data inserted into a materialized view is not subjected to unnecessary deduplication.
--   Executing a query to a Distributed table for which the local replica is lagging and remote replicas are unavailable does not result in an error anymore.
--   Users don’t need access permissions to the `default` database to create temporary tables anymore.
--   Fixed crashing when specifying the Array type without arguments.
--   Fixed hangups when the disk volume containing server logs is full.
--   Fixed an overflow in the toRelativeWeekNum function for the first week of the Unix epoch.
-
-#### Build improvements: {#build-improvements}
-
--   Several third-party libraries (notably Poco) were updated and converted to git submodules.
-
-### ClickHouse release 1.1.54304, 2017-10-19 {#clickhouse-release-1-1-54304-2017-10-19}
-
-#### New features: {#new-features-1}
-
--   TLS support in the native protocol (to enable, set `tcp_ssl_port` in `config.xml` ).
-
-#### Bug fixes: {#bug-fixes-1}
-
--   `ALTER` for replicated tables now tries to start running as soon as possible.
--   Fixed crashing when reading data with the setting `preferred_block_size_bytes=0.`
--   Fixed crashes of `clickhouse-client` when pressing `Page Down`
--   Correct interpretation of certain complex queries with `GLOBAL IN` and `UNION ALL`
--   `FREEZE PARTITION` always works atomically now.
--   Empty POST requests now return a response with code 411.
--   Fixed interpretation errors for expressions like `CAST(1 AS Nullable(UInt8)).`
--   Fixed an error when reading `Array(Nullable(String))` columns from `MergeTree` tables.
--   Fixed crashing when parsing queries like `SELECT dummy AS dummy, dummy AS b`
--   Users are updated correctly with invalid `users.xml`
--   Correct handling when an executable dictionary returns a non-zero response code.
-
-### ClickHouse release 1.1.54292, 2017-09-20 {#clickhouse-release-1-1-54292-2017-09-20}
-
-#### New features: {#new-features-2}
-
--   Added the `pointInPolygon` function for working with coordinates on a coordinate plane.
--   Added the `sumMap` aggregate function for calculating the sum of arrays, similar to `SummingMergeTree`.
--   Added the `trunc` function. Improved performance of the rounding functions (`round`, `floor`, `ceil`, `roundToExp2`) and corrected the logic of how they work. Changed the logic of the `roundToExp2` function for fractions and negative numbers.
--   The ClickHouse executable file is now less dependent on the libc version. The same ClickHouse executable file can run on a wide variety of Linux systems. There is still a dependency when using compiled queries (with the setting `compile = 1` , which is not used by default).
--   Reduced the time needed for dynamic compilation of queries.
-
-#### Bug fixes: {#bug-fixes-2}
-
--   Fixed an error that sometimes produced `part ... intersects previous part` messages and weakened replica consistency.
--   Fixed an error that caused the server to lock up if ZooKeeper was unavailable during shutdown.
--   Removed excessive logging when restoring replicas.
--   Fixed an error in the UNION ALL implementation.
--   Fixed an error in the concat function that occurred if the first column in a block has the Array type.
--   Progress is now displayed correctly in the system.merges table.
-
-### ClickHouse release 1.1.54289, 2017-09-13 {#clickhouse-release-1-1-54289-2017-09-13}
-
-#### New features: {#new-features-3}
-
--   `SYSTEM` queries for server administration: `SYSTEM RELOAD DICTIONARY`, `SYSTEM RELOAD DICTIONARIES`, `SYSTEM DROP DNS CACHE`, `SYSTEM SHUTDOWN`, `SYSTEM KILL`.
--   Added functions for working with arrays: `concat`, `arraySlice`, `arrayPushBack`, `arrayPushFront`, `arrayPopBack`, `arrayPopFront`.
--   Added `root` and `identity` parameters for the ZooKeeper configuration. This allows you to isolate individual users on the same ZooKeeper cluster.
--   Added aggregate functions `groupBitAnd`, `groupBitOr`, and `groupBitXor` (for compatibility, they are also available under the names `BIT_AND`, `BIT_OR`, and `BIT_XOR`).
--   External dictionaries can be loaded from MySQL by specifying a socket in the filesystem.
--   External dictionaries can be loaded from MySQL over SSL (`ssl_cert`, `ssl_key`, `ssl_ca` parameters).
--   Added the `max_network_bandwidth_for_user` setting to restrict the overall bandwidth use for queries per user.
--   Support for `DROP TABLE` for temporary tables.
--   Support for reading `DateTime` values in Unix timestamp format from the `CSV` and `JSONEachRow` formats.
--   Lagging replicas in distributed queries are now excluded by default (the default threshold is 5 minutes).
--   FIFO locking is used during ALTER: an ALTER query isn’t blocked indefinitely for continuously running queries.
--   Option to set `umask` in the config file.
--   Improved performance for queries with `DISTINCT` .
-
-#### Bug fixes: {#bug-fixes-3}
-
--   Improved the process for deleting old nodes in ZooKeeper. Previously, old nodes sometimes didn’t get deleted if there were very frequent inserts, which caused the server to be slow to shut down, among other things.
--   Fixed randomization when choosing hosts for the connection to ZooKeeper.
--   Fixed the exclusion of lagging replicas in distributed queries if the replica is localhost.
--   Fixed an error where a data part in a `ReplicatedMergeTree` table could be broken after running `ALTER MODIFY` on an element in a `Nested` structure.
--   Fixed an error that could cause SELECT queries to “hang”.
--   Improvements to distributed DDL queries.
--   Fixed the query `CREATE TABLE ... AS <materialized view>`.
--   Resolved the deadlock in the `ALTER ... CLEAR COLUMN IN PARTITION` query for `Buffer` tables.
--   Fixed the invalid default value for `Enum` s (0 instead of the minimum) when using the `JSONEachRow` and `TSKV` formats.
--   Resolved the appearance of zombie processes when using a dictionary with an `executable` source.
--   Fixed segfault for the HEAD query.
-
-#### Improved workflow for developing and assembling ClickHouse: {#improved-workflow-for-developing-and-assembling-clickhouse}
-
--   You can use `pbuilder` to build ClickHouse.
--   You can use `libc++` instead of `libstdc++` for builds on Linux.
--   Added instructions for using static code analysis tools: `Coverage`, `clang-tidy`, `cppcheck`.
-
-#### Please note when upgrading: {#please-note-when-upgrading}
-
--   There is now a higher default value for the MergeTree setting `max_bytes_to_merge_at_max_space_in_pool` (the maximum total size of data parts to merge, in bytes): it has increased from 100 GiB to 150 GiB. This might result in large merges running after the server upgrade, which could cause an increased load on the disk subsystem. If the free space available on the server is less than twice the total amount of the merges that are running, this will cause all other merges to stop running, including merges of small data parts. As a result, INSERT queries will fail with the message “Merges are processing significantly slower than inserts.” Use the `SELECT * FROM system.merges` query to monitor the situation. You can also check the `DiskSpaceReservedForMerge` metric in the `system.metrics` table, or in Graphite. You don’t need to do anything to fix this, since the issue will resolve itself once the large merges finish. If you find this unacceptable, you can restore the previous value for the `max_bytes_to_merge_at_max_space_in_pool` setting. To do this, go to the <merge_tree> section in config.xml, set ``` <merge_tree>``<max_bytes_to_merge_at_max_space_in_pool>107374182400</max_bytes_to_merge_at_max_space_in_pool> ``` and restart the server.
-
-### ClickHouse release 1.1.54284, 2017-08-29 {#clickhouse-release-1-1-54284-2017-08-29}
-
--   This is a bugfix release for the previous 1.1.54282 release. It fixes leaks in the parts directory in ZooKeeper.
-
-### ClickHouse release 1.1.54282, 2017-08-23 {#clickhouse-release-1-1-54282-2017-08-23}
-
-This release contains bug fixes for the previous release 1.1.54276:
-
--   Fixed `DB::Exception: Assertion violation: !_path.empty()` when inserting into a Distributed table.
--   Fixed parsing when inserting in RowBinary format if input data starts with’;’.
--   Errors during runtime compilation of certain aggregate functions (e.g. `groupArray()`).
-
-### Clickhouse Release 1.1.54276, 2017-08-16 {#clickhouse-release-1-1-54276-2017-08-16}
-
-#### New features: {#new-features-4}
-
--   Added an optional WITH section for a SELECT query. Example query: `WITH 1+1 AS a SELECT a, a*a`
--   INSERT can be performed synchronously in a Distributed table: OK is returned only after all the data is saved on all the shards. This is activated by the setting insert\_distributed\_sync=1.
--   Added the UUID data type for working with 16-byte identifiers.
--   Added aliases of CHAR, FLOAT and other types for compatibility with the Tableau.
--   Added the functions toYYYYMM, toYYYYMMDD, and toYYYYMMDDhhmmss for converting time into numbers.
--   You can use IP addresses (together with the hostname) to identify servers for clustered DDL queries.
--   Added support for non-constant arguments and negative offsets in the function `substring(str, pos, len).`
--   Added the max\_size parameter for the `groupArray(max_size)(column)` aggregate function, and optimized its performance.
-
-#### Main changes: {#main-changes}
-
--   Security improvements: all server files are created with 0640 permissions (can be changed via <umask> config parameter).
--   Improved error messages for queries with invalid syntax.
--   Significantly reduced memory consumption and improved performance when merging large sections of MergeTree data.
--   Significantly increased the performance of data merges for the ReplacingMergeTree engine.
--   Improved performance for asynchronous inserts from a Distributed table by combining multiple source inserts. To enable this functionality, use the setting distributed\_directory\_monitor\_batch\_inserts=1.
-
-#### Backward incompatible changes: {#backward-incompatible-changes-1}
-
--   Changed the binary format of aggregate states of `groupArray(array_column)` functions for arrays.
-
-#### Complete list of changes: {#complete-list-of-changes}
-
--   Added the `output_format_json_quote_denormals` setting, which enables outputting nan and inf values in JSON format.
--   Optimized stream allocation when reading from a Distributed table.
--   Settings can be configured in readonly mode if the value doesn’t change.
--   Added the ability to retrieve non-integer granules of the MergeTree engine in order to meet restrictions on the block size specified in the preferred\_block\_size\_bytes setting. The purpose is to reduce the consumption of RAM and increase cache locality when processing queries from tables with large columns.
--   Efficient use of indexes that contain expressions like `toStartOfHour(x)` for conditions like `toStartOfHour(x) op сonstexpr.`
--   Added new settings for MergeTree engines (the merge\_tree section in config.xml):
-    -   replicated\_deduplication\_window\_seconds sets the number of seconds allowed for deduplicating inserts in Replicated tables.
-    -   cleanup\_delay\_period sets how often to start cleanup to remove outdated data.
-    -   replicated\_can\_become\_leader can prevent a replica from becoming the leader (and assigning merges).
--   Accelerated cleanup to remove outdated data from ZooKeeper.
--   Multiple improvements and fixes for clustered DDL queries. Of particular interest is the new setting distributed\_ddl\_task\_timeout, which limits the time to wait for a response from the servers in the cluster. If a ddl request has not been performed on all hosts, a response will contain a timeout error and a request will be executed in an async mode.
--   Improved display of stack traces in the server logs.
--   Added the “none” value for the compression method.
--   You can use multiple dictionaries\_config sections in config.xml.
--   It is possible to connect to MySQL through a socket in the file system.
--   The system.parts table has a new column with information about the size of marks, in bytes.
-
-#### Bug fixes: {#bug-fixes-4}
-
--   Distributed tables using a Merge table now work correctly for a SELECT query with a condition on the `_table` field.
--   Fixed a rare race condition in ReplicatedMergeTree when checking data parts.
--   Fixed possible freezing on “leader election” when starting a server.
--   The max\_replica\_delay\_for\_distributed\_queries setting was ignored when using a local replica of the data source. This has been fixed.
--   Fixed incorrect behavior of `ALTER TABLE CLEAR COLUMN IN PARTITION` when attempting to clean a non-existing column.
--   Fixed an exception in the multiIf function when using empty arrays or strings.
--   Fixed excessive memory allocations when deserializing Native format.
--   Fixed incorrect auto-update of Trie dictionaries.
--   Fixed an exception when running queries with a GROUP BY clause from a Merge table when using SAMPLE.
--   Fixed a crash of GROUP BY when using distributed\_aggregation\_memory\_efficient=1.
--   Now you can specify the database.table in the right side of IN and JOIN.
--   Too many threads were used for parallel aggregation. This has been fixed.
--   Fixed how the “if” function works with FixedString arguments.
--   SELECT worked incorrectly from a Distributed table for shards with a weight of 0. This has been fixed.
--   Running `CREATE VIEW IF EXISTS no longer causes crashes.`
--   Fixed incorrect behavior when input\_format\_skip\_unknown\_fields=1 is set and there are negative numbers.
--   Fixed an infinite loop in the `dictGetHierarchy()` function if there is some invalid data in the dictionary.
--   Fixed `Syntax error: unexpected (...)` errors when running distributed queries with subqueries in an IN or JOIN clause and Merge tables.
--   Fixed an incorrect interpretation of a SELECT query from Dictionary tables.
--   Fixed the “Cannot mremap” error when using arrays in IN and JOIN clauses with more than 2 billion elements.
--   Fixed the failover for dictionaries with MySQL as the source.
-
-#### Improved workflow for developing and assembling ClickHouse: {#improved-workflow-for-developing-and-assembling-clickhouse-1}
-
--   Builds can be assembled in Arcadia.
--   You can use gcc 7 to compile ClickHouse.
--   Parallel builds using ccache+distcc are faster now.
-
-### ClickHouse release 1.1.54245, 2017-07-04 {#clickhouse-release-1-1-54245-2017-07-04}
-
-#### New features: {#new-features-5}
-
--   Distributed DDL (for example, `CREATE TABLE ON CLUSTER`)
--   The replicated query `ALTER TABLE CLEAR COLUMN IN PARTITION.`
--   The engine for Dictionary tables (access to dictionary data in the form of a table).
--   Dictionary database engine (this type of database automatically has Dictionary tables available for all the connected external dictionaries).
--   You can check for updates to the dictionary by sending a request to the source.
--   Qualified column names
--   Quoting identifiers using double quotation marks.
--   Sessions in the HTTP interface.
--   The OPTIMIZE query for a Replicated table can can run not only on the leader.
-
-#### Backward incompatible changes: {#backward-incompatible-changes-2}
-
--   Removed SET GLOBAL.
-
-#### Minor changes: {#minor-changes}
-
--   Now after an alert is triggered, the log prints the full stack trace.
--   Relaxed the verification of the number of damaged/extra data parts at startup (there were too many false positives).
-
-#### Bug fixes: {#bug-fixes-5}
-
--   Fixed a bad connection “sticking” when inserting into a Distributed table.
--   GLOBAL IN now works for a query from a Merge table that looks at a Distributed table.
--   The incorrect number of cores was detected on a Google Compute Engine virtual machine. This has been fixed.
--   Changes in how an executable source of cached external dictionaries works.
--   Fixed the comparison of strings containing null characters.
--   Fixed the comparison of Float32 primary key fields with constants.
--   Previously, an incorrect estimate of the size of a field could lead to overly large allocations.
--   Fixed a crash when querying a Nullable column added to a table using ALTER.
--   Fixed a crash when sorting by a Nullable column, if the number of rows is less than LIMIT.
--   Fixed an ORDER BY subquery consisting of only constant values.
--   Previously, a Replicated table could remain in the invalid state after a failed DROP TABLE.
--   Aliases for scalar subqueries with empty results are no longer lost.
--   Now a query that used compilation does not fail with an error if the .so file gets damaged.

docs/zh/changelog/index.md

@@ -1 +0,0 @@
-../../../CHANGELOG.md

docs/zh/changelog/index.md

@@ -0,0 +1,665 @@
+---
+machine_translated: true
+machine_translated_rev: b111334d6614a02564cf32f379679e9ff970d9b1
+---
+
+## 碌莽禄release拢.0755-88888888 {#clickhouse-release-v20-3}
+
+### ClickHouse版本v20.3.4.10,2020-03-20 {#clickhouse-release-v20-3-4-10-2020-03-20}
+
+#### 错误修复 {#bug-fix}
+
+-   此版本还包含20.1.8.41的所有错误修复
+-   修复丢失 `rows_before_limit_at_least` 用于通过http进行查询（使用处理器管道）。 这修复 [\#9730](https://github.com/ClickHouse/ClickHouse/issues/9730). [\#9757](https://github.com/ClickHouse/ClickHouse/pull/9757) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+
+### ClickHouse释放v20.3.3.6,2020-03-17 {#clickhouse-release-v20-3-3-6-2020-03-17}
+
+#### 错误修复 {#bug-fix-1}
+
+-   此版本还包含20.1.7.38的所有错误修复
+-   修复复制中的错误，如果用户在以前的版本上执行了突变，则不允许复制工作。 这修复 [\#9645](https://github.com/ClickHouse/ClickHouse/issues/9645). [\#9652](https://github.com/ClickHouse/ClickHouse/pull/9652) ([阿利沙平](https://github.com/alesapin)). 它使版本20.3再次向后兼容。
+-   添加设置 `use_compact_format_in_distributed_parts_names` 它允许写文件 `INSERT` 查询到 `Distributed` 表格格式更紧凑。 这修复 [\#9647](https://github.com/ClickHouse/ClickHouse/issues/9647). [\#9653](https://github.com/ClickHouse/ClickHouse/pull/9653) ([阿利沙平](https://github.com/alesapin)). 它使版本20.3再次向后兼容。
+
+### ClickHouse版本v20.3.2.1,2020-03-12 {#clickhouse-release-v20-3-2-1-2020-03-12}
+
+#### 向后不兼容的更改 {#backward-incompatible-change}
+
+-   修正了这个问题 `file name too long` 当发送数据 `Distributed` 大量副本的表。 修复了服务器日志中显示副本凭据的问题。 磁盘上的目录名格式已更改为 `[shard{shard_index}[_replica{replica_index}]]`. [\#8911](https://github.com/ClickHouse/ClickHouse/pull/8911) ([米哈伊尔\*科罗托夫](https://github.com/millb)）升级到新版本后，您将无法在没有人工干预的情况下降级，因为旧的服务器版本无法识别新的目录格式。 如果要降级，则必须手动将相应的目录重命名为旧格式。 仅当您使用了异步时，此更改才相关 `INSERT`s到 `Distributed` 桌子 在版本20.3.3中，我们将介绍一个设置，让您逐渐启用新格式。
+-   更改了mutation命令的复制日志条目的格式。 在安装新版本之前，您必须等待旧的突变处理。
+-   实现简单的内存分析器，将堆栈跟踪转储到 `system.trace_log` 超过软分配限制的每N个字节 [\#8765](https://github.com/ClickHouse/ClickHouse/pull/8765) ([伊万](https://github.com/abyss7)) [\#9472](https://github.com/ClickHouse/ClickHouse/pull/9472) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov)）列 `system.trace_log` 从改名 `timer_type` 到 `trace_type`. 这将需要改变第三方性能分析和flamegraph处理工具。
+-   在任何地方使用操作系统线程id，而不是内部线程编号。 这修复 [\#7477](https://github.com/ClickHouse/ClickHouse/issues/7477) 老 `clickhouse-client` 无法接收从服务器发送的日志，当设置 `send_logs_level` 已启用，因为结构化日志消息的名称和类型已更改。 另一方面，不同的服务器版本可以相互发送不同类型的日志。 当你不使用 `send_logs_level` 设置，你不应该关心。 [\#8954](https://github.com/ClickHouse/ClickHouse/pull/8954) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   删除 `indexHint` 功能 [\#9542](https://github.com/ClickHouse/ClickHouse/pull/9542) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   删除 `findClusterIndex`, `findClusterValue` 功能。 这修复 [\#8641](https://github.com/ClickHouse/ClickHouse/issues/8641). 如果您正在使用这些功能，请发送电子邮件至 `clickhouse-feedback@yandex-team.com` [\#9543](https://github.com/ClickHouse/ClickHouse/pull/9543) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   现在不允许创建列或添加列 `SELECT` 子查询作为默认表达式。 [\#9481](https://github.com/ClickHouse/ClickHouse/pull/9481) ([阿利沙平](https://github.com/alesapin))
+-   需要联接中的子查询的别名。 [\#9274](https://github.com/ClickHouse/ClickHouse/pull/9274) ([Artem Zuikov](https://github.com/4ertus2))
+-   改进 `ALTER MODIFY/ADD` 查询逻辑。 现在你不能 `ADD` 不带类型的列, `MODIFY` 默认表达式不改变列的类型和 `MODIFY` type不会丢失默认表达式值。 修复 [\#8669](https://github.com/ClickHouse/ClickHouse/issues/8669). [\#9227](https://github.com/ClickHouse/ClickHouse/pull/9227) ([阿利沙平](https://github.com/alesapin))
+-   要求重新启动服务器以应用日志记录配置中的更改。 这是一种临时解决方法，可以避免服务器将日志记录到已删除的日志文件中的错误（请参阅 [\#8696](https://github.com/ClickHouse/ClickHouse/issues/8696)). [\#8707](https://github.com/ClickHouse/ClickHouse/pull/8707) ([Alexander Kuzmenkov](https://github.com/akuzm))
+-   设置 `experimental_use_processors` 默认情况下启用。 此设置允许使用新的查询管道。 这是内部重构，我们期望没有明显的变化。 如果您将看到任何问题，请将其设置为返回零。 [\#8768](https://github.com/ClickHouse/ClickHouse/pull/8768) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+
+#### 新功能 {#new-feature}
+
+-   添加 `Avro` 和 `AvroConfluent` 输入/输出格式 [\#8571](https://github.com/ClickHouse/ClickHouse/pull/8571) ([安德鲁Onyshchuk](https://github.com/oandrew)) [\#8957](https://github.com/ClickHouse/ClickHouse/pull/8957) ([安德鲁Onyshchuk](https://github.com/oandrew)) [\#8717](https://github.com/ClickHouse/ClickHouse/pull/8717) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   过期密钥的多线程和非阻塞更新 `cache` 字典（可选的权限读取旧的）。 [\#8303](https://github.com/ClickHouse/ClickHouse/pull/8303) ([尼基塔\*米哈伊洛夫](https://github.com/nikitamikhaylov))
+-   添加查询 `ALTER ... MATERIALIZE TTL`. 它运行突变，强制通过TTL删除过期的数据，并重新计算所有部分有关ttl的元信息。 [\#8775](https://github.com/ClickHouse/ClickHouse/pull/8775) ([安东\*波波夫](https://github.com/CurtizJ))
+-   如果需要，从HashJoin切换到MergeJoin（在磁盘上 [\#9082](https://github.com/ClickHouse/ClickHouse/pull/9082) ([Artem Zuikov](https://github.com/4ertus2))
+-   已添加 `MOVE PARTITION` 命令 `ALTER TABLE` [\#4729](https://github.com/ClickHouse/ClickHouse/issues/4729) [\#6168](https://github.com/ClickHouse/ClickHouse/pull/6168) ([纪尧姆\*塔瑟里](https://github.com/YiuRULE))
+-   动态地从配置文件重新加载存储配置。 [\#8594](https://github.com/ClickHouse/ClickHouse/pull/8594) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   允许更改 `storage_policy` 为了不那么富有的人。 [\#8107](https://github.com/ClickHouse/ClickHouse/pull/8107) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   增加了对s3存储和表功能的globs/通配符的支持。 [\#8851](https://github.com/ClickHouse/ClickHouse/pull/8851) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   执行 `bitAnd`, `bitOr`, `bitXor`, `bitNot` 为 `FixedString(N)` 数据类型。 [\#9091](https://github.com/ClickHouse/ClickHouse/pull/9091) ([纪尧姆\*塔瑟里](https://github.com/YiuRULE))
+-   添加功能 `bitCount`. 这修复 [\#8702](https://github.com/ClickHouse/ClickHouse/issues/8702). [\#8708](https://github.com/ClickHouse/ClickHouse/pull/8708) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov)) [\#8749](https://github.com/ClickHouse/ClickHouse/pull/8749) ([ikopylov](https://github.com/ikopylov))
+-   添加 `generateRandom` 表函数生成具有给定模式的随机行。 允许用数据填充任意测试表。 [\#8994](https://github.com/ClickHouse/ClickHouse/pull/8994) ([Ilya Yatsishin](https://github.com/qoega))
+-   `JSONEachRowFormat`：当对象包含在顶层数组中时，支持特殊情况。 [\#8860](https://github.com/ClickHouse/ClickHouse/pull/8860) ([克鲁格洛夫\*帕维尔](https://github.com/Avogar))
+-   现在可以创建一个列 `DEFAULT` 取决于默认列的表达式 `ALIAS` 表达。 [\#9489](https://github.com/ClickHouse/ClickHouse/pull/9489) ([阿利沙平](https://github.com/alesapin))
+-   允许指定 `--limit` 超过源数据大小 `clickhouse-obfuscator`. 数据将以不同的随机种子重复。 [\#9155](https://github.com/ClickHouse/ClickHouse/pull/9155) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   已添加 `groupArraySample` 功能（类似于 `groupArray`）与reservior采样算法。 [\#8286](https://github.com/ClickHouse/ClickHouse/pull/8286) ([阿莫斯鸟](https://github.com/amosbird))
+-   现在，您可以监视更新队列的大小 `cache`/`complex_key_cache` 通过系统指标字典。 [\#9413](https://github.com/ClickHouse/ClickHouse/pull/9413) ([尼基塔\*米哈伊洛夫](https://github.com/nikitamikhaylov))
+-   允许使用CRLF作为CSV输出格式的行分隔符与设置 `output_format_csv_crlf_end_of_line` 设置为1 [\#8934](https://github.com/ClickHouse/ClickHouse/pull/8934) [\#8935](https://github.com/ClickHouse/ClickHouse/pull/8935) [\#8963](https://github.com/ClickHouse/ClickHouse/pull/8963) ([米哈伊尔\*科罗托夫](https://github.com/millb))
+-   实现的更多功能 [H3](https://github.com/uber/h3) API: `h3GetBaseCell`, `h3HexAreaM2`, `h3IndexesAreNeighbors`, `h3ToChildren`, `h3ToString` 和 `stringToH3` [\#8938](https://github.com/ClickHouse/ClickHouse/pull/8938) ([Nico Mandery](https://github.com/nmandery))
+-   引入新设置: `max_parser_depth` 控制最大堆栈大小并允许大型复杂查询。 这修复 [\#6681](https://github.com/ClickHouse/ClickHouse/issues/6681) 和 [\#7668](https://github.com/ClickHouse/ClickHouse/issues/7668). [\#8647](https://github.com/ClickHouse/ClickHouse/pull/8647) ([马克西姆\*斯米尔诺夫](https://github.com/qMBQx8GH))
+-   添加设置 `force_optimize_skip_unused_shards` 如果无法跳过未使用的分片，则设置为抛出 [\#8805](https://github.com/ClickHouse/ClickHouse/pull/8805) ([Azat Khuzhin](https://github.com/azat))
+-   允许配置多个磁盘/卷用于存储数据发送 `Distributed` 发动机 [\#8756](https://github.com/ClickHouse/ClickHouse/pull/8756) ([Azat Khuzhin](https://github.com/azat))
+-   支持存储策略 (`<tmp_policy>`）用于存储临时数据。 [\#8750](https://github.com/ClickHouse/ClickHouse/pull/8750) ([Azat Khuzhin](https://github.com/azat))
+-   已添加 `X-ClickHouse-Exception-Code` 如果在发送数据之前引发异常，则设置的HTTP头。 这实现了 [\#4971](https://github.com/ClickHouse/ClickHouse/issues/4971). [\#8786](https://github.com/ClickHouse/ClickHouse/pull/8786) ([米哈伊尔\*科罗托夫](https://github.com/millb))
+-   添加功能 `ifNotFinite`. 这只是一个句法糖: `ifNotFinite(x, y) = isFinite(x) ? x : y`. [\#8710](https://github.com/ClickHouse/ClickHouse/pull/8710) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   已添加 `last_successful_update_time` 列中 `system.dictionaries` 表 [\#9394](https://github.com/ClickHouse/ClickHouse/pull/9394) ([尼基塔\*米哈伊洛夫](https://github.com/nikitamikhaylov))
+-   添加 `blockSerializedSize` 功能（磁盘大小不压缩) [\#8952](https://github.com/ClickHouse/ClickHouse/pull/8952) ([Azat Khuzhin](https://github.com/azat))
+-   添加功能 `moduloOrZero` [\#9358](https://github.com/ClickHouse/ClickHouse/pull/9358) ([hcz](https://github.com/hczhcz))
+-   添加系统表 `system.zeros` 和 `system.zeros_mt` 以及故事功能 `zeros()` 和 `zeros_mt()`. 表（和表函数）包含具有名称的单列 `zero` 和类型 `UInt8`. 此列包含零。 为了测试目的，需要它作为生成许多行的最快方法。 这修复 [\#6604](https://github.com/ClickHouse/ClickHouse/issues/6604) [\#9593](https://github.com/ClickHouse/ClickHouse/pull/9593) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+
+#### 实验特点 {#experimental-feature}
+
+-   添加新的紧凑格式的部件 `MergeTree`-家庭表中的所有列都存储在一个文件中。 它有助于提高小型和频繁插入的性能。 旧的格式（每列一个文件）现在被称为wide。 数据存储格式由设置控制 `min_bytes_for_wide_part` 和 `min_rows_for_wide_part`. [\#8290](https://github.com/ClickHouse/ClickHouse/pull/8290) ([安东\*波波夫](https://github.com/CurtizJ))
+-   支持S3存储 `Log`, `TinyLog` 和 `StripeLog` 桌子 [\#8862](https://github.com/ClickHouse/ClickHouse/pull/8862) ([帕维尔\*科瓦连科](https://github.com/Jokser))
+
+#### 错误修复 {#bug-fix-2}
+
+-   修正了日志消息中不一致的空格。 [\#9322](https://github.com/ClickHouse/ClickHouse/pull/9322) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复在创建表时将未命名元组数组展平为嵌套结构的错误。 [\#8866](https://github.com/ClickHouse/ClickHouse/pull/8866) ([achulkov2](https://github.com/achulkov2))
+-   修复了以下问题 “Too many open files” 如果有太多的文件匹配glob模式可能会发生错误 `File` 表或 `file` 表功能。 现在文件懒洋洋地打开。 这修复 [\#8857](https://github.com/ClickHouse/ClickHouse/issues/8857) [\#8861](https://github.com/ClickHouse/ClickHouse/pull/8861) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   删除临时表现在只删除临时表。 [\#8907](https://github.com/ClickHouse/ClickHouse/pull/8907) ([维塔利\*巴拉诺夫](https://github.com/vitlibar))
+-   当我们关闭服务器或分离/附加表时删除过时的分区。 [\#8602](https://github.com/ClickHouse/ClickHouse/pull/8602) ([纪尧姆\*塔瑟里](https://github.com/YiuRULE))
+-   默认磁盘如何计算可用空间 `data` 子目录。 修复了可用空间量计算不正确的问题，如果 `data` 目录被安装到一个单独的设备（罕见的情况）。 这修复 [\#7441](https://github.com/ClickHouse/ClickHouse/issues/7441) [\#9257](https://github.com/ClickHouse/ClickHouse/pull/9257) ([米哈伊尔\*科罗托夫](https://github.com/millb))
+-   允许逗号（交叉）与IN（）内部连接。 [\#9251](https://github.com/ClickHouse/ClickHouse/pull/9251) ([Artem Zuikov](https://github.com/4ertus2))
+-   如果在WHERE部分中有\[NOT\]LIKE运算符，则允许将CROSS重写为INNER JOIN。 [\#9229](https://github.com/ClickHouse/ClickHouse/pull/9229) ([Artem Zuikov](https://github.com/4ertus2))
+-   修复后可能不正确的结果 `GROUP BY` 启用设置 `distributed_aggregation_memory_efficient`. 修复 [\#9134](https://github.com/ClickHouse/ClickHouse/issues/9134). [\#9289](https://github.com/ClickHouse/ClickHouse/pull/9289) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   找到的键在缓存字典的指标中被计为错过。 [\#9411](https://github.com/ClickHouse/ClickHouse/pull/9411) ([尼基塔\*米哈伊洛夫](https://github.com/nikitamikhaylov))
+-   修复引入的复制协议不兼容 [\#8598](https://github.com/ClickHouse/ClickHouse/issues/8598). [\#9412](https://github.com/ClickHouse/ClickHouse/pull/9412) ([阿利沙平](https://github.com/alesapin))
+-   在固定的竞争条件 `queue_task_handle` 在启动 `ReplicatedMergeTree` 桌子 [\#9552](https://github.com/ClickHouse/ClickHouse/pull/9552) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   令牌 `NOT` 没有工作 `SHOW TABLES NOT LIKE` 查询 [\#8727](https://github.com/ClickHouse/ClickHouse/issues/8727) [\#8940](https://github.com/ClickHouse/ClickHouse/pull/8940) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   添加范围检查功能 `h3EdgeLengthM`. 如果没有这个检查，缓冲区溢出是可能的。 [\#8945](https://github.com/ClickHouse/ClickHouse/pull/8945) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复了多个参数（超过10）的三元逻辑运算批量计算中的错误。 [\#8718](https://github.com/ClickHouse/ClickHouse/pull/8718) ([亚历山大\*卡扎科夫](https://github.com/Akazz))
+-   修复PREWHERE优化的错误，这可能导致段错误或 `Inconsistent number of columns got from MergeTreeRangeReader` 例外。 [\#9024](https://github.com/ClickHouse/ClickHouse/pull/9024) ([安东\*波波夫](https://github.com/CurtizJ))
+-   修复意外 `Timeout exceeded while reading from socket` 异常，在实际超时之前以及启用查询探查器时，在安全连接上随机发生。 还添加 `connect_timeout_with_failover_secure_ms` 设置（默认100ms），这是类似于 `connect_timeout_with_failover_ms`，但用于安全连接（因为SSL握手比普通TCP连接慢) [\#9026](https://github.com/ClickHouse/ClickHouse/pull/9026) ([tavplubix](https://github.com/tavplubix))
+-   修复突变最终确定的错误，当突变可能处于以下状态时 `parts_to_do=0` 和 `is_done=0`. [\#9022](https://github.com/ClickHouse/ClickHouse/pull/9022) ([阿利沙平](https://github.com/alesapin))
+-   使用新的任何连接逻辑 `partial_merge_join` 设置。 有可能使 `ANY|ALL|SEMI LEFT` 和 `ALL INNER` 加入与 `partial_merge_join=1` 现在 [\#8932](https://github.com/ClickHouse/ClickHouse/pull/8932) ([Artem Zuikov](https://github.com/4ertus2))
+-   Shard现在将从发起者获得的设置夹到shard的constaints，而不是抛出异常。 此修补程序允许将查询发送到具有另一个约束的分片。 [\#9447](https://github.com/ClickHouse/ClickHouse/pull/9447) ([维塔利\*巴拉诺夫](https://github.com/vitlibar))
+-   修正了内存管理问题 `MergeTreeReadPool`. [\#8791](https://github.com/ClickHouse/ClickHouse/pull/8791) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   修复 `toDecimal*OrNull()` 使用字符串调用时的函数系列 `e`. 修复 [\#8312](https://github.com/ClickHouse/ClickHouse/issues/8312) [\#8764](https://github.com/ClickHouse/ClickHouse/pull/8764) ([Artem Zuikov](https://github.com/4ertus2))
+-   请确保 `FORMAT Null` 不向客户端发送数据。 [\#8767](https://github.com/ClickHouse/ClickHouse/pull/8767) ([Alexander Kuzmenkov](https://github.com/akuzm))
+-   修复时间戳中的错误 `LiveViewBlockInputStream` 不会更新。 `LIVE VIEW` 是一个实验特征。 [\#8644](https://github.com/ClickHouse/ClickHouse/pull/8644) ([vxider](https://github.com/Vxider)) [\#8625](https://github.com/ClickHouse/ClickHouse/pull/8625) ([vxider](https://github.com/Vxider))
+-   固定 `ALTER MODIFY TTL` 不允许删除旧ttl表达式的错误行为。 [\#8422](https://github.com/ClickHouse/ClickHouse/pull/8422) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   修复了MergeTreeIndexSet中的UBSan报告。 这修复 [\#9250](https://github.com/ClickHouse/ClickHouse/issues/9250) [\#9365](https://github.com/ClickHouse/ClickHouse/pull/9365) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   固定的行为 `match` 和 `extract` 当干草堆有零字节的函数。 当干草堆不变时，这种行为是错误的。 这修复 [\#9160](https://github.com/ClickHouse/ClickHouse/issues/9160) [\#9163](https://github.com/ClickHouse/ClickHouse/pull/9163) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov)) [\#9345](https://github.com/ClickHouse/ClickHouse/pull/9345) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   避免从apache Avro第三方库中的析构函数抛出。 [\#9066](https://github.com/ClickHouse/ClickHouse/pull/9066) ([安德鲁Onyshchuk](https://github.com/oandrew))
+-   不要提交从轮询的批次 `Kafka` 部分，因为它可能会导致数据漏洞。 [\#8876](https://github.com/ClickHouse/ClickHouse/pull/8876) ([filimonov](https://github.com/filimonov))
+-   修复 `joinGet` 使用可为空的返回类型。 https://github.com/ClickHouse/ClickHouse/issues/8919 [\#9014](https://github.com/ClickHouse/ClickHouse/pull/9014) ([阿莫斯鸟](https://github.com/amosbird))
+-   修复压缩时的数据不兼容 `T64` 编解ec [\#9016](https://github.com/ClickHouse/ClickHouse/pull/9016) ([Artem Zuikov](https://github.com/4ertus2)）修复数据类型id `T64` 在受影响的版本中导致错误(de)压缩的压缩编解ec。 [\#9033](https://github.com/ClickHouse/ClickHouse/pull/9033) ([Artem Zuikov](https://github.com/4ertus2))
+-   添加设置 `enable_early_constant_folding` 并禁用它在某些情况下，导致错误。 [\#9010](https://github.com/ClickHouse/ClickHouse/pull/9010) ([Artem Zuikov](https://github.com/4ertus2))
+-   使用VIEW修复下推谓词优化器并启用测试 [\#9011](https://github.com/ClickHouse/ClickHouse/pull/9011) ([张冬](https://github.com/zhang2014))
+-   修复段错误 `Merge` 表，从读取时可能发生 `File` 储存 [\#9387](https://github.com/ClickHouse/ClickHouse/pull/9387) ([tavplubix](https://github.com/tavplubix))
+-   添加了对存储策略的检查 `ATTACH PARTITION FROM`, `REPLACE PARTITION`, `MOVE TO TABLE`. 否则，它可以使部分数据重新启动后无法访问，并阻止ClickHouse启动。 [\#9383](https://github.com/ClickHouse/ClickHouse/pull/9383) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   修复改变，如果有TTL设置表。 [\#8800](https://github.com/ClickHouse/ClickHouse/pull/8800) ([安东\*波波夫](https://github.com/CurtizJ))
+-   修复在以下情况下可能发生的竞争条件 `SYSTEM RELOAD ALL DICTIONARIES` 在某些字典被修改/添加/删除时执行。 [\#8801](https://github.com/ClickHouse/ClickHouse/pull/8801) ([维塔利\*巴拉诺夫](https://github.com/vitlibar))
+-   在以前的版本 `Memory` 数据库引擎使用空数据路径，因此在以下位置创建表 `path` directory (e.g. `/var/lib/clickhouse/`), not in data directory of database (e.g. `/var/lib/clickhouse/db_name`). [\#8753](https://github.com/ClickHouse/ClickHouse/pull/8753) ([tavplubix](https://github.com/tavplubix))
+-   修复了关于缺少默认磁盘或策略的错误日志消息。 [\#9530](https://github.com/ClickHouse/ClickHouse/pull/9530) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   修复数组类型的bloom\_filter索引的not(has())。 [\#9407](https://github.com/ClickHouse/ClickHouse/pull/9407) ([achimbab](https://github.com/achimbab))
+-   允许表中的第一列 `Log` 引擎是别名 [\#9231](https://github.com/ClickHouse/ClickHouse/pull/9231) ([伊万](https://github.com/abyss7))
+-   从读取时修复范围的顺序 `MergeTree` 表中的一个线程。 它可能会导致例外 `MergeTreeRangeReader` 或错误的查询结果。 [\#9050](https://github.com/ClickHouse/ClickHouse/pull/9050) ([安东\*波波夫](https://github.com/CurtizJ))
+-   赂眉露\>\> `reinterpretAsFixedString` 返回 `FixedString` 而不是 `String`. [\#9052](https://github.com/ClickHouse/ClickHouse/pull/9052) ([安德鲁Onyshchuk](https://github.com/oandrew))
+-   避免极少数情况下，当用户可以得到错误的错误消息 (`Success` 而不是详细的错误描述）。 [\#9457](https://github.com/ClickHouse/ClickHouse/pull/9457) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   使用时不要崩溃 `Template` 使用空行模板格式化。 [\#8785](https://github.com/ClickHouse/ClickHouse/pull/8785) ([Alexander Kuzmenkov](https://github.com/akuzm))
+-   系统表的元数据文件可能在错误的位置创建 [\#8653](https://github.com/ClickHouse/ClickHouse/pull/8653) ([tavplubix](https://github.com/tavplubix)）修复 [\#8581](https://github.com/ClickHouse/ClickHouse/issues/8581).
+-   修复缓存字典中exception\_ptr上的数据竞赛 [\#8303](https://github.com/ClickHouse/ClickHouse/issues/8303). [\#9379](https://github.com/ClickHouse/ClickHouse/pull/9379) ([尼基塔\*米哈伊洛夫](https://github.com/nikitamikhaylov))
+-   不要为查询引发异常 `ATTACH TABLE IF NOT EXISTS`. 以前它是抛出，如果表已经存在，尽管 `IF NOT EXISTS` 条款 [\#8967](https://github.com/ClickHouse/ClickHouse/pull/8967) ([安东\*波波夫](https://github.com/CurtizJ))
+-   修复了异常消息中丢失的关闭paren。 [\#8811](https://github.com/ClickHouse/ClickHouse/pull/8811) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   避免消息 `Possible deadlock avoided` 在clickhouse客户端在交互模式下启动。 [\#9455](https://github.com/ClickHouse/ClickHouse/pull/9455) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复了base64编码值末尾填充格式错误的问题。 更新base64库。 这修复 [\#9491](https://github.com/ClickHouse/ClickHouse/issues/9491)，关闭 [\#9492](https://github.com/ClickHouse/ClickHouse/issues/9492) [\#9500](https://github.com/ClickHouse/ClickHouse/pull/9500) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   防止丢失数据 `Kafka` 在极少数情况下，在读取后缀之后但在提交之前发生异常。 修复 [\#9378](https://github.com/ClickHouse/ClickHouse/issues/9378) [\#9507](https://github.com/ClickHouse/ClickHouse/pull/9507) ([filimonov](https://github.com/filimonov))
+-   在固定的异常 `DROP TABLE IF EXISTS` [\#8663](https://github.com/ClickHouse/ClickHouse/pull/8663) ([尼基塔\*瓦西列夫](https://github.com/nikvas0))
+-   修复当用户尝试崩溃 `ALTER MODIFY SETTING` 对于老格式化 `MergeTree` 表引擎家族. [\#9435](https://github.com/ClickHouse/ClickHouse/pull/9435) ([阿利沙平](https://github.com/alesapin))
+-   支持在JSON相关函数中不适合Int64的UInt64号码。 更新SIMDJSON掌握。 这修复 [\#9209](https://github.com/ClickHouse/ClickHouse/issues/9209) [\#9344](https://github.com/ClickHouse/ClickHouse/pull/9344) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   当使用非严格单调函数索引时，固定执行反转谓词。 [\#9223](https://github.com/ClickHouse/ClickHouse/pull/9223) ([亚历山大\*卡扎科夫](https://github.com/Akazz))
+-   不要试图折叠 `IN` 常量在 `GROUP BY` [\#8868](https://github.com/ClickHouse/ClickHouse/pull/8868) ([阿莫斯鸟](https://github.com/amosbird))
+-   修复bug `ALTER DELETE` 突变导致索引损坏。 这修复 [\#9019](https://github.com/ClickHouse/ClickHouse/issues/9019) 和 [\#8982](https://github.com/ClickHouse/ClickHouse/issues/8982). 另外修复极其罕见的竞争条件 `ReplicatedMergeTree` `ALTER` 查询。 [\#9048](https://github.com/ClickHouse/ClickHouse/pull/9048) ([阿利沙平](https://github.com/alesapin))
+-   当设置 `compile_expressions` 被启用，你可以得到 `unexpected column` 在 `LLVMExecutableFunction` 当我们使用 `Nullable` 类型 [\#8910](https://github.com/ClickHouse/ClickHouse/pull/8910) ([纪尧姆\*塔瑟里](https://github.com/YiuRULE))
+-   多个修复 `Kafka` 引擎：1）修复在消费者组重新平衡期间出现的重复项。 2)修复罕见 ‘holes’ 当数据从一个轮询的几个分区轮询并部分提交时出现（现在我们总是处理/提交整个轮询的消息块）。 3）通过块大小修复刷新（在此之前，只有超时刷新才能正常工作）。 4）更好的订阅程序（与分配反馈）。 5）使测试工作得更快（默认时间间隔和超时）。 由于数据之前没有被块大小刷新（根据文档），pr可能会导致默认设置的性能下降（由于更频繁和更小的刷新不太理想）。 如果您在更改后遇到性能问题-请增加 `kafka_max_block_size` 在表中的更大的值（例如 `CREATE TABLE ...Engine=Kafka ... SETTINGS ... kafka_max_block_size=524288`). 修复 [\#7259](https://github.com/ClickHouse/ClickHouse/issues/7259) [\#8917](https://github.com/ClickHouse/ClickHouse/pull/8917) ([filimonov](https://github.com/filimonov))
+-   修复 `Parameter out of bound` 在PREWHERE优化之后的某些查询中出现异常。 [\#8914](https://github.com/ClickHouse/ClickHouse/pull/8914) ([Baudouin Giard](https://github.com/bgiard))
+-   修正了函数参数混合常量的情况 `arrayZip`. [\#8705](https://github.com/ClickHouse/ClickHouse/pull/8705) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   执行时 `CREATE` 查询，在存储引擎参数中折叠常量表达式。 将空数据库名称替换为当前数据库。 修复 [\#6508](https://github.com/ClickHouse/ClickHouse/issues/6508), [\#3492](https://github.com/ClickHouse/ClickHouse/issues/3492) [\#9262](https://github.com/ClickHouse/ClickHouse/pull/9262) ([tavplubix](https://github.com/tavplubix))
+-   现在不可能创建或添加具有简单循环别名的列，如 `a DEFAULT b, b DEFAULT a`. [\#9603](https://github.com/ClickHouse/ClickHouse/pull/9603) ([阿利沙平](https://github.com/alesapin))
+-   修正了双重移动可能会损坏原始部分的错误。 这是相关的，如果你使用 `ALTER TABLE MOVE` [\#8680](https://github.com/ClickHouse/ClickHouse/pull/8680) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   允许 `interval` 用于正确解析的标识符，而无需反引号。 当一个查询不能被执行，即使固定的问题 `interval` 标识符用反引号或双引号括起来。 这修复 [\#9124](https://github.com/ClickHouse/ClickHouse/issues/9124). [\#9142](https://github.com/ClickHouse/ClickHouse/pull/9142) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修正了模糊测试和不正确的行为 `bitTestAll`/`bitTestAny` 功能。 [\#9143](https://github.com/ClickHouse/ClickHouse/pull/9143) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复可能的崩溃/错误的行数 `LIMIT n WITH TIES` 当有很多行等于第n行时。 [\#9464](https://github.com/ClickHouse/ClickHouse/pull/9464) ([tavplubix](https://github.com/tavplubix))
+-   使用enabled编写的部件修复突变 `insert_quorum`. [\#9463](https://github.com/ClickHouse/ClickHouse/pull/9463) ([阿利沙平](https://github.com/alesapin))
+-   修复数据竞赛破坏 `Poco::HTTPServer`. 当服务器启动并立即关闭时，可能会发生这种情况。 [\#9468](https://github.com/ClickHouse/ClickHouse/pull/9468) ([安东\*波波夫](https://github.com/CurtizJ))
+-   修复运行时显示误导性错误消息的错误 `SHOW CREATE TABLE a_table_that_does_not_exist`. [\#8899](https://github.com/ClickHouse/ClickHouse/pull/8899) ([achulkov2](https://github.com/achulkov2))
+-   固定 `Parameters are out of bound` 例外在一些罕见的情况下，当我们在一个常数 `SELECT` 条款时，我们有一个 `ORDER BY` 和一个 `LIMIT` 条款 [\#8892](https://github.com/ClickHouse/ClickHouse/pull/8892) ([纪尧姆\*塔瑟里](https://github.com/YiuRULE))
+-   修复突变定稿，当已经完成突变可以有状态 `is_done=0`. [\#9217](https://github.com/ClickHouse/ClickHouse/pull/9217) ([阿利沙平](https://github.com/alesapin))
+-   防止执行 `ALTER ADD INDEX` 对于旧语法的MergeTree表，因为它不起作用。 [\#8822](https://github.com/ClickHouse/ClickHouse/pull/8822) ([米哈伊尔\*科罗托夫](https://github.com/millb))
+-   在服务器启动时不要访问表，这 `LIVE VIEW` 取决于，所以服务器将能够启动。 也删除 `LIVE VIEW` 分离时的依赖关系 `LIVE VIEW`. `LIVE VIEW` 是一个实验特征。 [\#8824](https://github.com/ClickHouse/ClickHouse/pull/8824) ([tavplubix](https://github.com/tavplubix))
+-   修复可能的段错误 `MergeTreeRangeReader`，同时执行 `PREWHERE`. [\#9106](https://github.com/ClickHouse/ClickHouse/pull/9106) ([安东\*波波夫](https://github.com/CurtizJ))
+-   修复与列Ttl可能不匹配的校验和。 [\#9451](https://github.com/ClickHouse/ClickHouse/pull/9451) ([安东\*波波夫](https://github.com/CurtizJ))
+-   修正了一个错误，当部分没有被移动的情况下，只有一个卷的TTL规则在后台。 [\#8672](https://github.com/ClickHouse/ClickHouse/pull/8672) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   修正了这个问题 `Method createColumn() is not implemented for data type Set`. 这修复 [\#7799](https://github.com/ClickHouse/ClickHouse/issues/7799). [\#8674](https://github.com/ClickHouse/ClickHouse/pull/8674) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   现在我们将尝试更频繁地完成突变。 [\#9427](https://github.com/ClickHouse/ClickHouse/pull/9427) ([阿利沙平](https://github.com/alesapin))
+-   修复 `intDiv` 减一个常数 [\#9351](https://github.com/ClickHouse/ClickHouse/pull/9351) ([hcz](https://github.com/hczhcz))
+-   修复可能的竞争条件 `BlockIO`. [\#9356](https://github.com/ClickHouse/ClickHouse/pull/9356) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   修复尝试使用/删除时导致服务器终止的错误 `Kafka` 使用错误的参数创建的表。 [\#9513](https://github.com/ClickHouse/ClickHouse/pull/9513) ([filimonov](https://github.com/filimonov))
+-   增加了解决方法，如果操作系统返回错误的结果 `timer_create` 功能。 [\#8837](https://github.com/ClickHouse/ClickHouse/pull/8837) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   在使用固定错误 `min_marks_for_seek` 参数。 修复了分布式表中没有分片键时的错误消息，并且我们尝试跳过未使用的分片。 [\#8908](https://github.com/ClickHouse/ClickHouse/pull/8908) ([Azat Khuzhin](https://github.com/azat))
+
+#### 改进 {#improvement}
+
+-   执行 `ALTER MODIFY/DROP` 对突变的顶部查询 `ReplicatedMergeTree*` 引擎家族. 现在 `ALTERS` 仅在元数据更新阶段阻止，之后不阻止。 [\#8701](https://github.com/ClickHouse/ClickHouse/pull/8701) ([阿利沙平](https://github.com/alesapin))
+-   添加重写交叉到内部连接的能力 `WHERE` 包含未编译名称的部分。 [\#9512](https://github.com/ClickHouse/ClickHouse/pull/9512) ([Artem Zuikov](https://github.com/4ertus2))
+-   赂眉露\>\> `SHOW TABLES` 和 `SHOW DATABASES` 查询支持 `WHERE` 表达式和 `FROM`/`IN` [\#9076](https://github.com/ClickHouse/ClickHouse/pull/9076) ([sundyli](https://github.com/sundy-li))
+-   添加了一个设置 `deduplicate_blocks_in_dependent_materialized_views`. [\#9070](https://github.com/ClickHouse/ClickHouse/pull/9070) ([urykhy](https://github.com/urykhy))
+-   在最近的变化之后，MySQL客户端开始以十六进制打印二进制字符串，从而使它们不可读 ([\#9032](https://github.com/ClickHouse/ClickHouse/issues/9032)). ClickHouse中的解决方法是将字符串列标记为UTF-8，这并不总是如此，但通常是这种情况。 [\#9079](https://github.com/ClickHouse/ClickHouse/pull/9079) ([尤里\*巴拉诺夫](https://github.com/yurriy))
+-   添加对字符串和FixedString键的支持 `sumMap` [\#8903](https://github.com/ClickHouse/ClickHouse/pull/8903) ([Baudouin Giard](https://github.com/bgiard))
+-   支持SummingMergeTree地图中的字符串键 [\#8933](https://github.com/ClickHouse/ClickHouse/pull/8933) ([Baudouin Giard](https://github.com/bgiard))
+-   即使线程已抛出异常，也向线程池发送线程终止信号 [\#8736](https://github.com/ClickHouse/ClickHouse/pull/8736) ([丁香飞](https://github.com/dingxiangfei2009))
+-   允许设置 `query_id` 在 `clickhouse-benchmark` [\#9416](https://github.com/ClickHouse/ClickHouse/pull/9416) ([安东\*波波夫](https://github.com/CurtizJ))
+-   不要让奇怪的表达 `ALTER TABLE ... PARTITION partition` 查询。 这个地址 [\#7192](https://github.com/ClickHouse/ClickHouse/issues/7192) [\#8835](https://github.com/ClickHouse/ClickHouse/pull/8835) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   表 `system.table_engines` 现在提供有关功能支持的信息（如 `supports_ttl` 或 `supports_sort_order`). [\#8830](https://github.com/ClickHouse/ClickHouse/pull/8830) ([Max Akhmedov](https://github.com/zlobober))
+-   启用 `system.metric_log` 默认情况下。 它将包含具有ProfileEvents值的行，CurrentMetrics收集与 “collect\_interval\_milliseconds” 间隔（默认情况下为一秒）。 该表非常小（通常以兆字节为单位），默认情况下收集此数据是合理的。 [\#9225](https://github.com/ClickHouse/ClickHouse/pull/9225) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   Initialize query profiler for all threads in a group, e.g. it allows to fully profile insert-queries. Fixes [\#6964](https://github.com/ClickHouse/ClickHouse/issues/6964) [\#8874](https://github.com/ClickHouse/ClickHouse/pull/8874) ([伊万](https://github.com/abyss7))
+-   现在是暂时的 `LIVE VIEW` 创建者 `CREATE LIVE VIEW name WITH TIMEOUT [42] ...` 而不是 `CREATE TEMPORARY LIVE VIEW ...`，因为以前的语法不符合 `CREATE TEMPORARY TABLE ...` [\#9131](https://github.com/ClickHouse/ClickHouse/pull/9131) ([tavplubix](https://github.com/tavplubix))
+-   添加text\_log。级别配置参数，以限制进入 `system.text_log` 表 [\#8809](https://github.com/ClickHouse/ClickHouse/pull/8809) ([Azat Khuzhin](https://github.com/azat))
+-   允许根据TTL规则将下载的部分放入磁盘/卷 [\#8598](https://github.com/ClickHouse/ClickHouse/pull/8598) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   对于外部MySQL字典，允许将MySQL连接池共同化为 “share” 他们在字典中。 此选项显着减少到MySQL服务器的连接数。 [\#9409](https://github.com/ClickHouse/ClickHouse/pull/9409) ([Clément Rodriguez](https://github.com/clemrodriguez))
+-   显示分位数的最近查询执行时间 `clickhouse-benchmark` 输出而不是插值值。 最好显示与某些查询的执行时间相对应的值。 [\#8712](https://github.com/ClickHouse/ClickHouse/pull/8712) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   可以在将数据插入到Kafka时为消息添加密钥和时间戳。 修复 [\#7198](https://github.com/ClickHouse/ClickHouse/issues/7198) [\#8969](https://github.com/ClickHouse/ClickHouse/pull/8969) ([filimonov](https://github.com/filimonov))
+-   如果服务器从终端运行，请按颜色突出显示线程号，查询id和日志优先级。 这是为了提高开发人员相关日志消息的可读性。 [\#8961](https://github.com/ClickHouse/ClickHouse/pull/8961) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   更好的异常消息，同时加载表 `Ordinary` 数据库。 [\#9527](https://github.com/ClickHouse/ClickHouse/pull/9527) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   执行 `arraySlice` 对于具有聚合函数状态的数组。 这修复 [\#9388](https://github.com/ClickHouse/ClickHouse/issues/9388) [\#9391](https://github.com/ClickHouse/ClickHouse/pull/9391) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   允许在in运算符的右侧使用常量函数和常量数组。 [\#8813](https://github.com/ClickHouse/ClickHouse/pull/8813) ([安东\*波波夫](https://github.com/CurtizJ))
+-   如果在获取系统数据时发生了zookeeper异常。副本，将其显示在单独的列中。 这实现了 [\#9137](https://github.com/ClickHouse/ClickHouse/issues/9137) [\#9138](https://github.com/ClickHouse/ClickHouse/pull/9138) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   原子删除destroy上的MergeTree数据部分。 [\#8402](https://github.com/ClickHouse/ClickHouse/pull/8402) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   支持分布式表的行级安全性。 [\#8926](https://github.com/ClickHouse/ClickHouse/pull/8926) ([伊万](https://github.com/abyss7))
+-   Now we recognize suffix (like KB, KiB…) in settings values. [\#8072](https://github.com/ClickHouse/ClickHouse/pull/8072) ([米哈伊尔\*科罗托夫](https://github.com/millb))
+-   在构建大型连接的结果时防止内存不足。 [\#8637](https://github.com/ClickHouse/ClickHouse/pull/8637) ([Artem Zuikov](https://github.com/4ertus2))
+-   在交互模式下为建议添加群集名称 `clickhouse-client`. [\#8709](https://github.com/ClickHouse/ClickHouse/pull/8709) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   Initialize query profiler for all threads in a group, e.g. it allows to fully profile insert-queries [\#8820](https://github.com/ClickHouse/ClickHouse/pull/8820) ([伊万](https://github.com/abyss7))
+-   添加列 `exception_code` 在 `system.query_log` 桌子 [\#8770](https://github.com/ClickHouse/ClickHouse/pull/8770) ([米哈伊尔\*科罗托夫](https://github.com/millb))
+-   在端口上启用MySQL兼容服务器 `9004` 在默认服务器配置文件中。 在配置的例子固定密码生成命令。 [\#8771](https://github.com/ClickHouse/ClickHouse/pull/8771) ([尤里\*巴拉诺夫](https://github.com/yurriy))
+-   如果文件系统是只读的，请防止在关闭时中止。 这修复 [\#9094](https://github.com/ClickHouse/ClickHouse/issues/9094) [\#9100](https://github.com/ClickHouse/ClickHouse/pull/9100) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   当HTTP POST查询中需要长度时，更好的异常消息。 [\#9453](https://github.com/ClickHouse/ClickHouse/pull/9453) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   添加 `_path` 和 `_file` 虚拟列 `HDFS` 和 `File` 发动机和 `hdfs` 和 `file` 表函数 [\#8489](https://github.com/ClickHouse/ClickHouse/pull/8489) ([Olga Khvostikova](https://github.com/stavrolia))
+-   修复错误 `Cannot find column` 同时插入到 `MATERIALIZED VIEW` 在情况下，如果新列被添加到视图的内部表。 [\#8766](https://github.com/ClickHouse/ClickHouse/pull/8766) [\#8788](https://github.com/ClickHouse/ClickHouse/pull/8788) ([vzakaznikov](https://github.com/vzakaznikov)) [\#8788](https://github.com/ClickHouse/ClickHouse/issues/8788) [\#8806](https://github.com/ClickHouse/ClickHouse/pull/8806) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai)) [\#8803](https://github.com/ClickHouse/ClickHouse/pull/8803) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   通过最终更新后发送进度（如日志）修复本机客户端-服务器协议的进度。 这可能仅与使用本机协议的某些第三方工具相关。 [\#9495](https://github.com/ClickHouse/ClickHouse/pull/9495) ([Azat Khuzhin](https://github.com/azat))
+-   添加系统指标跟踪使用MySQL协议的客户端连接数 ([\#9013](https://github.com/ClickHouse/ClickHouse/issues/9013)). [\#9015](https://github.com/ClickHouse/ClickHouse/pull/9015) ([尤金\*克里莫夫](https://github.com/Slach))
+-   从现在开始，HTTP响应将有 `X-ClickHouse-Timezone` 标题设置为相同的时区值 `SELECT timezone()` 会报告。 [\#9493](https://github.com/ClickHouse/ClickHouse/pull/9493) ([Denis Glazachev](https://github.com/traceon))
+
+#### 性能改进 {#performance-improvement}
+
+-   使用IN提高分析指标的性能 [\#9261](https://github.com/ClickHouse/ClickHouse/pull/9261) ([安东\*波波夫](https://github.com/CurtizJ))
+-   逻辑函数+代码清理更简单，更有效的代码。 跟进到 [\#8718](https://github.com/ClickHouse/ClickHouse/issues/8718) [\#8728](https://github.com/ClickHouse/ClickHouse/pull/8728) ([亚历山大\*卡扎科夫](https://github.com/Akazz))
+-   整体性能改善（范围为5％。.通过确保使用C++20功能进行更严格的别名处理，对于受影响的查询来说，这是200％）。 [\#9304](https://github.com/ClickHouse/ClickHouse/pull/9304) ([阿莫斯鸟](https://github.com/amosbird))
+-   比较函数的内部循环更严格的别名。 [\#9327](https://github.com/ClickHouse/ClickHouse/pull/9327) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   对于算术函数的内部循环更严格的别名。 [\#9325](https://github.com/ClickHouse/ClickHouse/pull/9325) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   ColumnVector::replicate()的实现速度快约3倍，通过该实现ColumnConst::convertToFullColumn()。 在实现常数时，也将在测试中有用。 [\#9293](https://github.com/ClickHouse/ClickHouse/pull/9293) ([亚历山大\*卡扎科夫](https://github.com/Akazz))
+-   另一个小的性能改进 `ColumnVector::replicate()` （这加快了 `materialize` 函数和高阶函数），甚至进一步改进 [\#9293](https://github.com/ClickHouse/ClickHouse/issues/9293) [\#9442](https://github.com/ClickHouse/ClickHouse/pull/9442) ([亚历山大\*卡扎科夫](https://github.com/Akazz))
+-   改进的性能 `stochasticLinearRegression` 聚合函数。 此补丁由英特尔贡献。 [\#8652](https://github.com/ClickHouse/ClickHouse/pull/8652) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   提高性能 `reinterpretAsFixedString` 功能。 [\#9342](https://github.com/ClickHouse/ClickHouse/pull/9342) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   不要向客户端发送块 `Null` 处理器管道中的格式。 [\#8797](https://github.com/ClickHouse/ClickHouse/pull/8797) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai)) [\#8767](https://github.com/ClickHouse/ClickHouse/pull/8767) ([Alexander Kuzmenkov](https://github.com/akuzm))
+
+#### 构建/测试/包装改进 {#buildtestingpackaging-improvement}
+
+-   异常处理现在可以在适用于Linux的Windows子系统上正常工作。 看https://github.com/ClickHouse-Extras/libunwind/pull/3 这修复 [\#6480](https://github.com/ClickHouse/ClickHouse/issues/6480) [\#9564](https://github.com/ClickHouse/ClickHouse/pull/9564) ([sobolevsv](https://github.com/sobolevsv))
+-   替换 `readline` 与 `replxx` 对于在交互式线编辑 `clickhouse-client` [\#8416](https://github.com/ClickHouse/ClickHouse/pull/8416) ([伊万](https://github.com/abyss7))
+-   在FunctionsComparison中更好的构建时间和更少的模板实例化。 [\#9324](https://github.com/ClickHouse/ClickHouse/pull/9324) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   增加了与集成 `clang-tidy` 在线人 另请参阅 [\#6044](https://github.com/ClickHouse/ClickHouse/issues/6044) [\#9566](https://github.com/ClickHouse/ClickHouse/pull/9566) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   现在我们使用CI链接ClickHouse `lld` 即使是 `gcc`. [\#9049](https://github.com/ClickHouse/ClickHouse/pull/9049) ([阿利沙平](https://github.com/alesapin))
+-   允许随机线程调度和插入毛刺时 `THREAD_FUZZER_*` 设置环境变量。 这有助于测试。 [\#9459](https://github.com/ClickHouse/ClickHouse/pull/9459) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   在无状态测试中启用安全套接字 [\#9288](https://github.com/ClickHouse/ClickHouse/pull/9288) ([tavplubix](https://github.com/tavplubix))
+-   使SPLIT\_SHARED\_LIBRARIES=OFF更强大 [\#9156](https://github.com/ClickHouse/ClickHouse/pull/9156) ([Azat Khuzhin](https://github.com/azat))
+-   赂眉露\>\> “performance\_introspection\_and\_logging” 测试可靠的随机服务器卡住。 这可能发生在CI环境中。 另请参阅 [\#9515](https://github.com/ClickHouse/ClickHouse/issues/9515) [\#9528](https://github.com/ClickHouse/ClickHouse/pull/9528) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   在样式检查中验证XML。 [\#9550](https://github.com/ClickHouse/ClickHouse/pull/9550) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修正了测试中的竞争条件 `00738_lock_for_inner_table`. 这个测试依赖于睡眠。 [\#9555](https://github.com/ClickHouse/ClickHouse/pull/9555) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   删除类型的性能测试 `once`. 这是在统计比较模式下运行所有性能测试（更可靠）所需的。 [\#9557](https://github.com/ClickHouse/ClickHouse/pull/9557) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   增加了算术函数的性能测试。 [\#9326](https://github.com/ClickHouse/ClickHouse/pull/9326) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   增加了性能测试 `sumMap` 和 `sumMapWithOverflow` 聚合函数。 后续行动 [\#8933](https://github.com/ClickHouse/ClickHouse/issues/8933) [\#8947](https://github.com/ClickHouse/ClickHouse/pull/8947) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   通过样式检查确保错误代码的样式。 [\#9370](https://github.com/ClickHouse/ClickHouse/pull/9370) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   为测试历史添加脚本。 [\#8796](https://github.com/ClickHouse/ClickHouse/pull/8796) ([阿利沙平](https://github.com/alesapin))
+-   添加GCC警告 `-Wsuggest-override` 找到并修复所有地方 `override` 必须使用关键字。 [\#8760](https://github.com/ClickHouse/ClickHouse/pull/8760) ([kreuzerkrieg](https://github.com/kreuzerkrieg))
+-   在Mac OS X下忽略弱符号，因为它必须被定义 [\#9538](https://github.com/ClickHouse/ClickHouse/pull/9538) ([已删除用户](https://github.com/ghost))
+-   规范性能测试中某些查询的运行时间。 这是在准备在比较模式下运行所有性能测试时完成的。 [\#9565](https://github.com/ClickHouse/ClickHouse/pull/9565) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复一些测试，以支持pytest与查询测试 [\#9062](https://github.com/ClickHouse/ClickHouse/pull/9062) ([伊万](https://github.com/abyss7))
+-   使用MSan在生成中启用SSL，因此在运行无状态测试时，服务器不会在启动时失败 [\#9531](https://github.com/ClickHouse/ClickHouse/pull/9531) ([tavplubix](https://github.com/tavplubix))
+-   修复测试结果中的数据库替换 [\#9384](https://github.com/ClickHouse/ClickHouse/pull/9384) ([Ilya Yatsishin](https://github.com/qoega))
+-   针对其他平台构建修复程序 [\#9381](https://github.com/ClickHouse/ClickHouse/pull/9381) ([proller](https://github.com/proller)) [\#8755](https://github.com/ClickHouse/ClickHouse/pull/8755) ([proller](https://github.com/proller)) [\#8631](https://github.com/ClickHouse/ClickHouse/pull/8631) ([proller](https://github.com/proller))
+-   将磁盘部分添加到无状态复盖率测试docker映像 [\#9213](https://github.com/ClickHouse/ClickHouse/pull/9213) ([帕维尔\*科瓦连科](https://github.com/Jokser))
+-   使用GRPC构建时，摆脱源代码树中的文件 [\#9588](https://github.com/ClickHouse/ClickHouse/pull/9588) ([阿莫斯鸟](https://github.com/amosbird))
+-   通过从上下文中删除SessionCleaner来缩短构建时间。 让SessionCleaner的代码更简单。 [\#9232](https://github.com/ClickHouse/ClickHouse/pull/9232) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   更新了clickhouse-test脚本中挂起查询的检查 [\#8858](https://github.com/ClickHouse/ClickHouse/pull/8858) ([亚历山大\*卡扎科夫](https://github.com/Akazz))
+-   从存储库中删除了一些无用的文件。 [\#8843](https://github.com/ClickHouse/ClickHouse/pull/8843) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   更改类型的数学perftests从 `once` 到 `loop`. [\#8783](https://github.com/ClickHouse/ClickHouse/pull/8783) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   添加码头镜像，它允许为我们的代码库构建交互式代码浏览器HTML报告。 [\#8781](https://github.com/ClickHouse/ClickHouse/pull/8781) ([阿利沙平](https://github.com/alesapin)）见 [Woboq代码浏览器](https://clickhouse-test-reports.s3.yandex.net/codebrowser/html_report///ClickHouse/dbms/index.html)
+-   抑制MSan下的一些测试失败。 [\#8780](https://github.com/ClickHouse/ClickHouse/pull/8780) ([Alexander Kuzmenkov](https://github.com/akuzm))
+-   加速 “exception while insert” 测试 此测试通常在具有复盖率的调试版本中超时。 [\#8711](https://github.com/ClickHouse/ClickHouse/pull/8711) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   更新 `libcxx` 和 `libcxxabi` 为了主人 在准备 [\#9304](https://github.com/ClickHouse/ClickHouse/issues/9304) [\#9308](https://github.com/ClickHouse/ClickHouse/pull/9308) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复flacky测试 `00910_zookeeper_test_alter_compression_codecs`. [\#9525](https://github.com/ClickHouse/ClickHouse/pull/9525) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   清理重复的链接器标志。 确保链接器不会查找意想不到的符号。 [\#9433](https://github.com/ClickHouse/ClickHouse/pull/9433) ([阿莫斯鸟](https://github.com/amosbird))
+-   添加 `clickhouse-odbc` 驱动程序进入测试图像。 这允许通过自己的ODBC驱动程序测试ClickHouse与ClickHouse的交互。 [\#9348](https://github.com/ClickHouse/ClickHouse/pull/9348) ([filimonov](https://github.com/filimonov))
+-   修复单元测试中的几个错误。 [\#9047](https://github.com/ClickHouse/ClickHouse/pull/9047) ([阿利沙平](https://github.com/alesapin))
+-   启用 `-Wmissing-include-dirs` GCC警告消除所有不存在的包括-主要是由于CMake脚本错误 [\#8704](https://github.com/ClickHouse/ClickHouse/pull/8704) ([kreuzerkrieg](https://github.com/kreuzerkrieg))
+-   描述查询探查器无法工作的原因。 这是用于 [\#9049](https://github.com/ClickHouse/ClickHouse/issues/9049) [\#9144](https://github.com/ClickHouse/ClickHouse/pull/9144) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   将OpenSSL更新到上游主机。 修复了TLS连接可能会失败并显示消息的问题 `OpenSSL SSL_read: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error` 和 `SSL Exception: error:2400006E:random number generator::error retrieving entropy`. 该问题出现在版本20.1中。 [\#8956](https://github.com/ClickHouse/ClickHouse/pull/8956) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   更新服务器的Dockerfile [\#8893](https://github.com/ClickHouse/ClickHouse/pull/8893) ([Ilya Mazaev](https://github.com/ne-ray))
+-   Build-gcc-from-sources脚本中的小修复 [\#8774](https://github.com/ClickHouse/ClickHouse/pull/8774) ([Michael Nacharov](https://github.com/mnach))
+-   替换 `numbers` 到 `zeros` 在perftests其中 `number` 不使用列。 这将导致更干净的测试结果。 [\#9600](https://github.com/ClickHouse/ClickHouse/pull/9600) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   修复列构造函数中使用initializer\_list时堆栈溢出问题。 [\#9367](https://github.com/ClickHouse/ClickHouse/pull/9367) ([已删除用户](https://github.com/ghost))
+-   将librdkafka升级到v1.3.0。 启用bund绑 `rdkafka` 和 `gsasl` mac OS X上的库 [\#9000](https://github.com/ClickHouse/ClickHouse/pull/9000) ([安德鲁Onyshchuk](https://github.com/oandrew))
+-   在GCC9.2.0上构建修复程序 [\#9306](https://github.com/ClickHouse/ClickHouse/pull/9306) ([vxider](https://github.com/Vxider))
+
+## 碌莽禄.拢.0755-88888888 {#clickhouse-release-v20-1}
+
+### ClickHouse版本v20.1.8.41,2020-03-20 {#clickhouse-release-v20-1-8-41-2020-03-20}
+
+#### 错误修复 {#bug-fix-3}
+
+-   修复可能的永久性 `Cannot schedule a task` 错误（由于未处理的异常 `ParallelAggregatingBlockInputStream::Handler::onFinish/onFinishThread`). 这修复 [\#6833](https://github.com/ClickHouse/ClickHouse/issues/6833). [\#9154](https://github.com/ClickHouse/ClickHouse/pull/9154) ([Azat Khuzhin](https://github.com/azat))
+-   修复过多的内存消耗 `ALTER` 查询（突变）。 这修复 [\#9533](https://github.com/ClickHouse/ClickHouse/issues/9533) 和 [\#9670](https://github.com/ClickHouse/ClickHouse/issues/9670). [\#9754](https://github.com/ClickHouse/ClickHouse/pull/9754) ([阿利沙平](https://github.com/alesapin))
+-   修复外部字典DDL中反引用的错误。 这修复 [\#9619](https://github.com/ClickHouse/ClickHouse/issues/9619). [\#9734](https://github.com/ClickHouse/ClickHouse/pull/9734) ([阿利沙平](https://github.com/alesapin))
+
+### ClickHouse释放v20.1.7.38,2020-03-18 {#clickhouse-release-v20-1-7-38-2020-03-18}
+
+#### 错误修复 {#bug-fix-4}
+
+-   修正了不正确的内部函数名称 `sumKahan` 和 `sumWithOverflow`. 在远程查询中使用此函数时，我会导致异常。 [\#9636](https://github.com/ClickHouse/ClickHouse/pull/9636) ([Azat Khuzhin](https://github.com/azat)). 这个问题是在所有ClickHouse版本。
+-   允许 `ALTER ON CLUSTER` 的 `Distributed` 具有内部复制的表。 这修复 [\#3268](https://github.com/ClickHouse/ClickHouse/issues/3268). [\#9617](https://github.com/ClickHouse/ClickHouse/pull/9617) ([shinoi2](https://github.com/shinoi2)). 这个问题是在所有ClickHouse版本。
+-   修复可能的异常 `Size of filter doesn't match size of column` 和 `Invalid number of rows in Chunk` 在 `MergeTreeRangeReader`. 它们可能在执行时出现 `PREWHERE` 在某些情况下。 修复 [\#9132](https://github.com/ClickHouse/ClickHouse/issues/9132). [\#9612](https://github.com/ClickHouse/ClickHouse/pull/9612) ([安东\*波波夫](https://github.com/CurtizJ))
+-   修复了这个问题：如果你编写一个简单的算术表达式，则不会保留时区 `time + 1` （与像这样的表达形成对比 `time + INTERVAL 1 SECOND`). 这修复 [\#5743](https://github.com/ClickHouse/ClickHouse/issues/5743). [\#9323](https://github.com/ClickHouse/ClickHouse/pull/9323) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov)). 这个问题是在所有ClickHouse版本。
+-   现在不可能创建或添加具有简单循环别名的列，如 `a DEFAULT b, b DEFAULT a`. [\#9603](https://github.com/ClickHouse/ClickHouse/pull/9603) ([阿利沙平](https://github.com/alesapin))
+-   修复了base64编码值末尾填充格式错误的问题。 更新base64库。 这修复 [\#9491](https://github.com/ClickHouse/ClickHouse/issues/9491)，关闭 [\#9492](https://github.com/ClickHouse/ClickHouse/issues/9492) [\#9500](https://github.com/ClickHouse/ClickHouse/pull/9500) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复数据竞赛破坏 `Poco::HTTPServer`. 当服务器启动并立即关闭时，可能会发生这种情况。 [\#9468](https://github.com/ClickHouse/ClickHouse/pull/9468) ([安东\*波波夫](https://github.com/CurtizJ))
+-   修复可能的崩溃/错误的行数 `LIMIT n WITH TIES` 当有很多行等于第n行时。 [\#9464](https://github.com/ClickHouse/ClickHouse/pull/9464) ([tavplubix](https://github.com/tavplubix))
+-   修复与列Ttl可能不匹配的校验和。 [\#9451](https://github.com/ClickHouse/ClickHouse/pull/9451) ([安东\*波波夫](https://github.com/CurtizJ))
+-   修复当用户尝试崩溃 `ALTER MODIFY SETTING` 对于老格式化 `MergeTree` 表引擎家族. [\#9435](https://github.com/ClickHouse/ClickHouse/pull/9435) ([阿利沙平](https://github.com/alesapin))
+-   现在我们将尝试更频繁地完成突变。 [\#9427](https://github.com/ClickHouse/ClickHouse/pull/9427) ([阿利沙平](https://github.com/alesapin))
+-   修复引入的复制协议不兼容 [\#8598](https://github.com/ClickHouse/ClickHouse/issues/8598). [\#9412](https://github.com/ClickHouse/ClickHouse/pull/9412) ([阿利沙平](https://github.com/alesapin))
+-   修复数组类型的bloom\_filter索引的not(has())。 [\#9407](https://github.com/ClickHouse/ClickHouse/pull/9407) ([achimbab](https://github.com/achimbab))
+-   固定的行为 `match` 和 `extract` 当干草堆有零字节的函数。 当干草堆不变时，这种行为是错误的。 这修复 [\#9160](https://github.com/ClickHouse/ClickHouse/issues/9160) [\#9163](https://github.com/ClickHouse/ClickHouse/pull/9163) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov)) [\#9345](https://github.com/ClickHouse/ClickHouse/pull/9345) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+
+#### 构建/测试/包装改进 {#buildtestingpackaging-improvement-1}
+
+-   异常处理现在可以在适用于Linux的Windows子系统上正常工作。 看https://github.com/ClickHouse-Extras/libunwind/pull/3 这修复 [\#6480](https://github.com/ClickHouse/ClickHouse/issues/6480) [\#9564](https://github.com/ClickHouse/ClickHouse/pull/9564) ([sobolevsv](https://github.com/sobolevsv))
+
+### ClickHouse释放v20.1.6.30,2020-03-05 {#clickhouse-release-v20-1-6-30-2020-03-05}
+
+#### 错误修复 {#bug-fix-5}
+
+-   修复压缩时的数据不兼容 `T64` 编解ec
+    [\#9039](https://github.com/ClickHouse/ClickHouse/pull/9039) [（abyss7)](https://github.com/abyss7)
+-   在一个线程中从MergeTree表中读取时修复范围顺序。 修复 [\#8964](https://github.com/ClickHouse/ClickHouse/issues/8964).
+    [\#9050](https://github.com/ClickHouse/ClickHouse/pull/9050) [(CurtizJ))](https://github.com/CurtizJ)
+-   修复可能的段错误 `MergeTreeRangeReader`，同时执行 `PREWHERE`. 修复 [\#9064](https://github.com/ClickHouse/ClickHouse/issues/9064).
+    [\#9106](https://github.com/ClickHouse/ClickHouse/pull/9106) [(CurtizJ))](https://github.com/CurtizJ)
+-   修复 `reinterpretAsFixedString` 返回 `FixedString` 而不是 `String`.
+    [\#9052](https://github.com/ClickHouse/ClickHouse/pull/9052) [(oandrew)](https://github.com/oandrew)
+-   修复 `joinGet` 使用可为空的返回类型。 修复 [\#8919](https://github.com/ClickHouse/ClickHouse/issues/8919)
+    [\#9014](https://github.com/ClickHouse/ClickHouse/pull/9014) [（amosbird)](https://github.com/amosbird)
+-   修复bittestall/bitTestAny函数的模糊测试和不正确的行为。
+    [\#9143](https://github.com/ClickHouse/ClickHouse/pull/9143) [（阿列克谢-米洛维多夫)](https://github.com/alexey-milovidov)
+-   修复当干草堆有零字节时匹配和提取函数的行为。 当干草堆不变时，这种行为是错误的。 修复 [\#9160](https://github.com/ClickHouse/ClickHouse/issues/9160)
+    [\#9163](https://github.com/ClickHouse/ClickHouse/pull/9163) [（阿列克谢-米洛维多夫)](https://github.com/alexey-milovidov)
+-   当使用非严格单调函数索引时，固定执行反转谓词。 修复 [\#9034](https://github.com/ClickHouse/ClickHouse/issues/9034)
+    [\#9223](https://github.com/ClickHouse/ClickHouse/pull/9223) [（Akazz)](https://github.com/Akazz)
+-   允许重写 `CROSS` 到 `INNER JOIN` 如果有 `[NOT] LIKE` 操作员在 `WHERE` 科。 修复 [\#9191](https://github.com/ClickHouse/ClickHouse/issues/9191)
+    [\#9229](https://github.com/ClickHouse/ClickHouse/pull/9229) [(4ertus2)](https://github.com/4ertus2)
+-   允许使用日志引擎的表中的第一列成为别名。
+    [\#9231](https://github.com/ClickHouse/ClickHouse/pull/9231) [（abyss7)](https://github.com/abyss7)
+-   允许逗号加入 `IN()` 进去 修复 [\#7314](https://github.com/ClickHouse/ClickHouse/issues/7314).
+    [\#9251](https://github.com/ClickHouse/ClickHouse/pull/9251) [(4ertus2)](https://github.com/4ertus2)
+-   改进 `ALTER MODIFY/ADD` 查询逻辑。 现在你不能 `ADD` 不带类型的列, `MODIFY` 默认表达式不改变列的类型和 `MODIFY` type不会丢失默认表达式值。 修复 [\#8669](https://github.com/ClickHouse/ClickHouse/issues/8669).
+    [\#9227](https://github.com/ClickHouse/ClickHouse/pull/9227) [(alesapin)](https://github.com/alesapin)
+-   修复突变最终确定，当已经完成突变时可以具有状态is\_done=0。
+    [\#9217](https://github.com/ClickHouse/ClickHouse/pull/9217) [(alesapin)](https://github.com/alesapin)
+-   碌莽禄Support: “Processors” 管道系统.数字和系统.numbers\_mt 这也修复了错误时 `max_execution_time` 不被尊重。
+    [\#7796](https://github.com/ClickHouse/ClickHouse/pull/7796) [(KochetovNicolai)](https://github.com/KochetovNicolai)
+-   修复错误的计数 `DictCacheKeysRequestedFound` 公制。
+    [\#9411](https://github.com/ClickHouse/ClickHouse/pull/9411) [(nikitamikhaylov)](https://github.com/nikitamikhaylov)
+-   添加了对存储策略的检查 `ATTACH PARTITION FROM`, `REPLACE PARTITION`, `MOVE TO TABLE` 否则可能使部分数据在重新启动后无法访问，并阻止ClickHouse启动。
+    [\#9383](https://github.com/ClickHouse/ClickHouse/pull/9383) [（excitoon)](https://github.com/excitoon)
+-   在固定的瑞银报告 `MergeTreeIndexSet`. 这修复 [\#9250](https://github.com/ClickHouse/ClickHouse/issues/9250)
+    [\#9365](https://github.com/ClickHouse/ClickHouse/pull/9365) [（阿列克谢-米洛维多夫)](https://github.com/alexey-milovidov)
+-   在BlockIO中修复可能的数据集。
+    [\#9356](https://github.com/ClickHouse/ClickHouse/pull/9356) [(KochetovNicolai)](https://github.com/KochetovNicolai)
+-   支持 `UInt64` 在JSON相关函数中不适合Int64的数字。 更新 `SIMDJSON` 为了主人 这修复 [\#9209](https://github.com/ClickHouse/ClickHouse/issues/9209)
+    [\#9344](https://github.com/ClickHouse/ClickHouse/pull/9344) [（阿列克谢-米洛维多夫)](https://github.com/alexey-milovidov)
+-   如果将数据目录挂载到单独的设备，则修复可用空间量计算不正确时的问题。 对于默认磁盘，计算数据子目录的可用空间。 这修复 [\#7441](https://github.com/ClickHouse/ClickHouse/issues/7441)
+    [\#9257](https://github.com/ClickHouse/ClickHouse/pull/9257) [（米尔布)](https://github.com/millb)
+-   修复TLS连接可能会失败并显示消息时的问题 `OpenSSL SSL_read: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error and SSL Exception: error:2400006E:random number generator::error retrieving entropy.` 将OpenSSL更新到上游主机。
+    [\#8956](https://github.com/ClickHouse/ClickHouse/pull/8956) [（阿列克谢-米洛维多夫)](https://github.com/alexey-milovidov)
+-   执行时 `CREATE` 查询，在存储引擎参数中折叠常量表达式。 将空数据库名称替换为当前数据库。 修复 [\#6508](https://github.com/ClickHouse/ClickHouse/issues/6508), [\#3492](https://github.com/ClickHouse/ClickHouse/issues/3492). 还修复了ClickHouseDictionarySource中检查本地地址。
+    [\#9262](https://github.com/ClickHouse/ClickHouse/pull/9262) [（tabplubix)](https://github.com/tavplubix)
+-   修复段错误 `StorageMerge`，从StorageFile读取时可能发生。
+    [\#9387](https://github.com/ClickHouse/ClickHouse/pull/9387) [（tabplubix)](https://github.com/tavplubix)
+-   防止丢失数据 `Kafka` 在极少数情况下，在读取后缀之后但在提交之前发生异常。 修复 [\#9378](https://github.com/ClickHouse/ClickHouse/issues/9378). 相关: [\#7175](https://github.com/ClickHouse/ClickHouse/issues/7175)
+    [\#9507](https://github.com/ClickHouse/ClickHouse/pull/9507) [(菲利蒙诺夫)](https://github.com/filimonov)
+-   修复尝试使用/删除时导致服务器终止的错误 `Kafka` 使用错误的参数创建的表。 修复 [\#9494](https://github.com/ClickHouse/ClickHouse/issues/9494). 结合 [\#9507](https://github.com/ClickHouse/ClickHouse/issues/9507).
+    [\#9513](https://github.com/ClickHouse/ClickHouse/pull/9513) [(菲利蒙诺夫)](https://github.com/filimonov)
+
+#### 新功能 {#new-feature-1}
+
+-   添加 `deduplicate_blocks_in_dependent_materialized_views` 用于控制具有实例化视图的表中幂等插入的行为的选项。 这个新功能是由Altinity的特殊要求添加到错误修正版本中的。
+    [\#9070](https://github.com/ClickHouse/ClickHouse/pull/9070) [(urykhy)](https://github.com/urykhy)
+
+### ClickHouse版本v20.1.2.4,2020-01-22 {#clickhouse-release-v20-1-2-4-2020-01-22}
+
+#### 向后不兼容的更改 {#backward-incompatible-change-1}
+
+-   使设置 `merge_tree_uniform_read_distribution` 过时了 服务器仍可识别此设置，但无效。 [\#8308](https://github.com/ClickHouse/ClickHouse/pull/8308) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   更改函数的返回类型 `greatCircleDistance` 到 `Float32` 因为现在计算的结果是 `Float32`. [\#7993](https://github.com/ClickHouse/ClickHouse/pull/7993) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   现在预计查询参数表示为 “escaped” 格式。 例如，要传递字符串 `a<tab>b` 你必须写 `a\tb` 或 `a\<tab>b` 并分别, `a%5Ctb` 或 `a%5C%09b` 在URL中。 这是需要添加传递NULL作为的可能性 `\N`. 这修复 [\#7488](https://github.com/ClickHouse/ClickHouse/issues/7488). [\#8517](https://github.com/ClickHouse/ClickHouse/pull/8517) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   启用 `use_minimalistic_part_header_in_zookeeper` 设置 `ReplicatedMergeTree` 默认情况下。 这将显着减少存储在ZooKeeper中的数据量。 自19.1版本以来支持此设置，我们已经在多个服务的生产中使用它，半年以上没有任何问题。 如果您有机会降级到19.1以前的版本，请禁用此设置。 [\#6850](https://github.com/ClickHouse/ClickHouse/pull/6850) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   数据跳过索引已准备就绪并默认启用。 设置 `allow_experimental_data_skipping_indices`, `allow_experimental_cross_to_join_conversion` 和 `allow_experimental_multiple_joins_emulation` 现在已经过时，什么也不做。 [\#7974](https://github.com/ClickHouse/ClickHouse/pull/7974) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   添加新建 `ANY JOIN` 逻辑 `StorageJoin` 符合 `JOIN` 操作。 要在不改变行为的情况下进行升级，您需要添加 `SETTINGS any_join_distinct_right_table_keys = 1` 引擎联接表元数据或在升级后重新创建这些表。 [\#8400](https://github.com/ClickHouse/ClickHouse/pull/8400) ([Artem Zuikov](https://github.com/4ertus2))
+-   要求重新启动服务器以应用日志记录配置中的更改。 这是一种临时解决方法，可以避免服务器将日志记录到已删除的日志文件中的错误（请参阅 [\#8696](https://github.com/ClickHouse/ClickHouse/issues/8696)). [\#8707](https://github.com/ClickHouse/ClickHouse/pull/8707) ([Alexander Kuzmenkov](https://github.com/akuzm))
+
+#### 新功能 {#new-feature-2}
+
+-   添加了有关部件路径的信息 `system.merges`. [\#8043](https://github.com/ClickHouse/ClickHouse/pull/8043) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   添加执行能力 `SYSTEM RELOAD DICTIONARY` 查询中 `ON CLUSTER` 模式 [\#8288](https://github.com/ClickHouse/ClickHouse/pull/8288) ([纪尧姆\*塔瑟里](https://github.com/YiuRULE))
+-   添加执行能力 `CREATE DICTIONARY` 查询中 `ON CLUSTER` 模式 [\#8163](https://github.com/ClickHouse/ClickHouse/pull/8163) ([阿利沙平](https://github.com/alesapin))
+-   现在用户的个人资料 `users.xml` 可以继承多个配置文件。 [\#8343](https://github.com/ClickHouse/ClickHouse/pull/8343) ([Mikhail f. Shiryaev](https://github.com/Felixoid))
+-   已添加 `system.stack_trace` 允许查看所有服务器线程的堆栈跟踪的表。 这对于开发人员反省服务器状态非常有用。 这修复 [\#7576](https://github.com/ClickHouse/ClickHouse/issues/7576). [\#8344](https://github.com/ClickHouse/ClickHouse/pull/8344) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   添加 `DateTime64` 具有可配置子秒精度的数据类型。 [\#7170](https://github.com/ClickHouse/ClickHouse/pull/7170) ([瓦西里\*内姆科夫](https://github.com/Enmk))
+-   添加表函数 `clusterAllReplicas` 这允许查询集群中的所有节点。 [\#8493](https://github.com/ClickHouse/ClickHouse/pull/8493) ([kiran sunkari](https://github.com/kiransunkari))
+-   添加聚合函数 `categoricalInformationValue` 其计算出离散特征的信息值。 [\#8117](https://github.com/ClickHouse/ClickHouse/pull/8117) ([hcz](https://github.com/hczhcz))
+-   加快数据文件的解析 `CSV`, `TSV` 和 `JSONEachRow` 通过并行进行格式化。 [\#7780](https://github.com/ClickHouse/ClickHouse/pull/7780) ([Alexander Kuzmenkov](https://github.com/akuzm))
+-   添加功能 `bankerRound` 它执行银行家的四舍五入。 [\#8112](https://github.com/ClickHouse/ClickHouse/pull/8112) ([hcz](https://github.com/hczhcz))
+-   支持区域名称的嵌入式字典中的更多语言: ‘ru’, ‘en’, ‘ua’, ‘uk’, ‘by’, ‘kz’, ‘tr’, ‘de’, ‘uz’, ‘lv’, ‘lt’, ‘et’, ‘pt’, ‘he’, ‘vi’. [\#8189](https://github.com/ClickHouse/ClickHouse/pull/8189) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   改进的一致性 `ANY JOIN` 逻辑 现在 `t1 ANY LEFT JOIN t2` 等于 `t2 ANY RIGHT JOIN t1`. [\#7665](https://github.com/ClickHouse/ClickHouse/pull/7665) ([Artem Zuikov](https://github.com/4ertus2))
+-   添加设置 `any_join_distinct_right_table_keys` 这使旧的行为 `ANY INNER JOIN`. [\#7665](https://github.com/ClickHouse/ClickHouse/pull/7665) ([Artem Zuikov](https://github.com/4ertus2))
+-   添加新建 `SEMI` 和 `ANTI JOIN`. 老 `ANY INNER JOIN` 行为现在可作为 `SEMI LEFT JOIN`. [\#7665](https://github.com/ClickHouse/ClickHouse/pull/7665) ([Artem Zuikov](https://github.com/4ertus2))
+-   已添加 `Distributed` 格式 `File` 发动机和 `file` 表函数，它允许从读 `.bin` 通过异步插入生成的文件 `Distributed` 桌子 [\#8535](https://github.com/ClickHouse/ClickHouse/pull/8535) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   添加可选的重置列参数 `runningAccumulate` 这允许为每个新的键值重置聚合结果。 [\#8326](https://github.com/ClickHouse/ClickHouse/pull/8326) ([谢尔盖\*科诺年科](https://github.com/kononencheg))
+-   添加使用ClickHouse作为普罗米修斯端点的能力。 [\#7900](https://github.com/ClickHouse/ClickHouse/pull/7900) ([vdimir](https://github.com/Vdimir))
+-   添加部分 `<remote_url_allow_hosts>` 在 `config.xml` 这将限制允许的主机用于远程表引擎和表函数 `URL`, `S3`, `HDFS`. [\#7154](https://github.com/ClickHouse/ClickHouse/pull/7154) ([米哈伊尔\*科罗托夫](https://github.com/millb))
+-   添加功能 `greatCircleAngle` 它计算球体上的距离（以度为单位）。 [\#8105](https://github.com/ClickHouse/ClickHouse/pull/8105) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   改变地球半径与h3库一致。 [\#8105](https://github.com/ClickHouse/ClickHouse/pull/8105) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   已添加 `JSONCompactEachRow` 和 `JSONCompactEachRowWithNamesAndTypes` 输入和输出格式。 [\#7841](https://github.com/ClickHouse/ClickHouse/pull/7841) ([米哈伊尔\*科罗托夫](https://github.com/millb))
+-   增加了与文件相关的表引擎和表函数的功能 (`File`, `S3`, `URL`, `HDFS`）它允许读取和写入 `gzip` 基于附加引擎参数或文件扩展名的文件。 [\#7840](https://github.com/ClickHouse/ClickHouse/pull/7840) ([安德烈\*博德罗夫](https://github.com/apbodrov))
+-   添加了 `randomASCII(length)` 函数，生成一个字符串与一个随机集 [ASCII](https://en.wikipedia.org/wiki/ASCII#Printable_characters) 可打印字符。 [\#8401](https://github.com/ClickHouse/ClickHouse/pull/8401) ([刺刀](https://github.com/BayoNet))
+-   添加功能 `JSONExtractArrayRaw` 它返回从未解析的json数组元素上的数组 `JSON` 字符串。 [\#8081](https://github.com/ClickHouse/ClickHouse/pull/8081) ([Oleg Matrokhin](https://github.com/errx))
+-   添加 `arrayZip` 函数允许将多个长度相等的数组合成一个元组数组。 [\#8149](https://github.com/ClickHouse/ClickHouse/pull/8149) ([张冬](https://github.com/zhang2014))
+-   添加根据配置的磁盘之间移动数据的能力 `TTL`-表达式为 `*MergeTree` 表引擎家族. [\#8140](https://github.com/ClickHouse/ClickHouse/pull/8140) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   增加了新的聚合功能 `avgWeighted` 其允许计算加权平均值。 [\#7898](https://github.com/ClickHouse/ClickHouse/pull/7898) ([安德烈\*博德罗夫](https://github.com/apbodrov))
+-   现在并行解析默认启用 `TSV`, `TSKV`, `CSV` 和 `JSONEachRow` 格式。 [\#7894](https://github.com/ClickHouse/ClickHouse/pull/7894) ([尼基塔\*米哈伊洛夫](https://github.com/nikitamikhaylov))
+-   从添加几个地理功能 `H3` 图书馆: `h3GetResolution`, `h3EdgeAngle`, `h3EdgeLength`, `h3IsValid` 和 `h3kRing`. [\#8034](https://github.com/ClickHouse/ClickHouse/pull/8034) ([Konstantin Malanchev](https://github.com/hombit))
+-   增加了对brotli的支持 (`br`）压缩文件相关的存储和表函数。 这修复 [\#8156](https://github.com/ClickHouse/ClickHouse/issues/8156). [\#8526](https://github.com/ClickHouse/ClickHouse/pull/8526) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   添加 `groupBit*` 功能的 `SimpleAggregationFunction` 类型。 [\#8485](https://github.com/ClickHouse/ClickHouse/pull/8485) ([纪尧姆\*塔瑟里](https://github.com/YiuRULE))
+
+#### 错误修复 {#bug-fix-6}
+
+-   修复重命名表 `Distributed` 引擎 修复问题 [\#7868](https://github.com/ClickHouse/ClickHouse/issues/7868). [\#8306](https://github.com/ClickHouse/ClickHouse/pull/8306) ([tavplubix](https://github.com/tavplubix))
+-   现在字典支持 `EXPRESSION` 对于非ClickHouse SQL方言中任意字符串中的属性。 [\#8098](https://github.com/ClickHouse/ClickHouse/pull/8098) ([阿利沙平](https://github.com/alesapin))
+-   修复损坏 `INSERT SELECT FROM mysql(...)` 查询。 这修复 [\#8070](https://github.com/ClickHouse/ClickHouse/issues/8070) 和 [\#7960](https://github.com/ClickHouse/ClickHouse/issues/7960). [\#8234](https://github.com/ClickHouse/ClickHouse/pull/8234) ([tavplubix](https://github.com/tavplubix))
+-   修复错误 “Mismatch column sizes” 插入默认值时 `Tuple` 从 `JSONEachRow`. 这修复 [\#5653](https://github.com/ClickHouse/ClickHouse/issues/5653). [\#8606](https://github.com/ClickHouse/ClickHouse/pull/8606) ([tavplubix](https://github.com/tavplubix))
+-   现在将在使用的情况下抛出一个异常 `WITH TIES` 旁边的 `LIMIT BY`. 还增加了使用能力 `TOP` 与 `LIMIT BY`. 这修复 [\#7472](https://github.com/ClickHouse/ClickHouse/issues/7472). [\#7637](https://github.com/ClickHouse/ClickHouse/pull/7637) ([尼基塔\*米哈伊洛夫](https://github.com/nikitamikhaylov))
+-   从新鲜的glibc版本中修复unintendent依赖关系 `clickhouse-odbc-bridge` 二进制 [\#8046](https://github.com/ClickHouse/ClickHouse/pull/8046) ([阿莫斯鸟](https://github.com/amosbird))
+-   修正错误的检查功能 `*MergeTree` 引擎家族. 现在，当我们在最后一个颗粒和最后一个标记（非最终）中有相同数量的行时，它不会失败。 [\#8047](https://github.com/ClickHouse/ClickHouse/pull/8047) ([阿利沙平](https://github.com/alesapin))
+-   修复插入 `Enum*` 列后 `ALTER` 查询，当基础数值类型等于表指定类型时。 这修复 [\#7836](https://github.com/ClickHouse/ClickHouse/issues/7836). [\#7908](https://github.com/ClickHouse/ClickHouse/pull/7908) ([安东\*波波夫](https://github.com/CurtizJ))
+-   允许非常数负 “size” 函数的参数 `substring`. 这是不允许的错误。 这修复 [\#4832](https://github.com/ClickHouse/ClickHouse/issues/4832). [\#7703](https://github.com/ClickHouse/ClickHouse/pull/7703) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复当错误数量的参数传递到解析错误 `(O|J)DBC` 表引擎。 [\#7709](https://github.com/ClickHouse/ClickHouse/pull/7709) ([阿利沙平](https://github.com/alesapin))
+-   将日志发送到syslog时使用正在运行的clickhouse进程的命令名。 在以前的版本中，使用空字符串而不是命令名称。 [\#8460](https://github.com/ClickHouse/ClickHouse/pull/8460) ([Michael Nacharov](https://github.com/mnach))
+-   修复检查允许的主机 `localhost`. 这个公关修复了在提供的解决方案 [\#8241](https://github.com/ClickHouse/ClickHouse/pull/8241). [\#8342](https://github.com/ClickHouse/ClickHouse/pull/8342) ([维塔利\*巴拉诺夫](https://github.com/vitlibar))
+-   修复罕见的崩溃 `argMin` 和 `argMax` 长字符串参数的函数，当结果被用于 `runningAccumulate` 功能。 这修复 [\#8325](https://github.com/ClickHouse/ClickHouse/issues/8325) [\#8341](https://github.com/ClickHouse/ClickHouse/pull/8341) ([恐龙](https://github.com/769344359))
+-   修复表的内存过度使用 `Buffer` 引擎 [\#8345](https://github.com/ClickHouse/ClickHouse/pull/8345) ([Azat Khuzhin](https://github.com/azat))
+-   修正了可以采取的功能中的潜在错误 `NULL` 作为参数之一，并返回非NULL。 [\#8196](https://github.com/ClickHouse/ClickHouse/pull/8196) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   在线程池中更好地计算后台进程的指标 `MergeTree` 表引擎. [\#8194](https://github.com/ClickHouse/ClickHouse/pull/8194) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   修复功能 `IN` 里面 `WHERE` 存在行级表筛选器时的语句。 修复 [\#6687](https://github.com/ClickHouse/ClickHouse/issues/6687) [\#8357](https://github.com/ClickHouse/ClickHouse/pull/8357) ([伊万](https://github.com/abyss7))
+-   现在，如果整数值没有完全解析设置值，则会引发异常。 [\#7678](https://github.com/ClickHouse/ClickHouse/pull/7678) ([米哈伊尔\*科罗托夫](https://github.com/millb))
+-   修复当聚合函数用于查询具有两个以上本地分片的分布式表时出现的异常。 [\#8164](https://github.com/ClickHouse/ClickHouse/pull/8164) ([小路](https://github.com/nicelulu))
+-   现在，bloom filter可以处理零长度数组，并且不执行冗余计算。 [\#8242](https://github.com/ClickHouse/ClickHouse/pull/8242) ([achimbab](https://github.com/achimbab))
+-   修正了通过匹配客户端主机来检查客户端主机是否允许 `host_regexp` 在指定 `users.xml`. [\#8241](https://github.com/ClickHouse/ClickHouse/pull/8241) ([维塔利\*巴拉诺夫](https://github.com/vitlibar))
+-   放松不明确的列检查，导致多个误报 `JOIN ON` 科。 [\#8385](https://github.com/ClickHouse/ClickHouse/pull/8385) ([Artem Zuikov](https://github.com/4ertus2))
+-   修正了可能的服务器崩溃 (`std::terminate`)当服务器不能发送或写入数据 `JSON` 或 `XML` 格式与值 `String` 数据类型（需要 `UTF-8` 验证）或使用Brotli算法或其他一些罕见情况下压缩结果数据时。 这修复 [\#7603](https://github.com/ClickHouse/ClickHouse/issues/7603) [\#8384](https://github.com/ClickHouse/ClickHouse/pull/8384) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复竞争条件 `StorageDistributedDirectoryMonitor` 被线人发现 这修复 [\#8364](https://github.com/ClickHouse/ClickHouse/issues/8364). [\#8383](https://github.com/ClickHouse/ClickHouse/pull/8383) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   现在背景合并 `*MergeTree` 表引擎家族更准确地保留存储策略卷顺序。 [\#8549](https://github.com/ClickHouse/ClickHouse/pull/8549) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   现在表引擎 `Kafka` 与正常工作 `Native` 格式。 这修复 [\#6731](https://github.com/ClickHouse/ClickHouse/issues/6731) [\#7337](https://github.com/ClickHouse/ClickHouse/issues/7337) [\#8003](https://github.com/ClickHouse/ClickHouse/issues/8003). [\#8016](https://github.com/ClickHouse/ClickHouse/pull/8016) ([filimonov](https://github.com/filimonov))
+-   固定格式与标题（如 `CSVWithNames`）这是抛出关于EOF表引擎的异常 `Kafka`. [\#8016](https://github.com/ClickHouse/ClickHouse/pull/8016) ([filimonov](https://github.com/filimonov))
+-   修复了从子查询右侧部分制作set的错误 `IN` 科。 这修复 [\#5767](https://github.com/ClickHouse/ClickHouse/issues/5767) 和 [\#2542](https://github.com/ClickHouse/ClickHouse/issues/2542). [\#7755](https://github.com/ClickHouse/ClickHouse/pull/7755) ([尼基塔\*米哈伊洛夫](https://github.com/nikitamikhaylov))
+-   从存储读取时修复可能的崩溃 `File`. [\#7756](https://github.com/ClickHouse/ClickHouse/pull/7756) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   在固定的文件读取 `Parquet` 包含类型列的格式 `list`. [\#8334](https://github.com/ClickHouse/ClickHouse/pull/8334) ([马苏兰](https://github.com/maxulan))
+-   修复错误 `Not found column` 对于分布式查询 `PREWHERE` 条件取决于采样键if `max_parallel_replicas > 1`. [\#7913](https://github.com/ClickHouse/ClickHouse/pull/7913) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   修复错误 `Not found column` 如果使用查询 `PREWHERE` 依赖于表的别名，结果集由于主键条件而为空。 [\#7911](https://github.com/ClickHouse/ClickHouse/pull/7911) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   函数的固定返回类型 `rand` 和 `randConstant` 在情况下 `Nullable` 争论。 现在函数总是返回 `UInt32` 而且从来没有 `Nullable(UInt32)`. [\#8204](https://github.com/ClickHouse/ClickHouse/pull/8204) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   禁用谓词下推 `WITH FILL` 表达。 这修复 [\#7784](https://github.com/ClickHouse/ClickHouse/issues/7784). [\#7789](https://github.com/ClickHouse/ClickHouse/pull/7789) ([张冬](https://github.com/zhang2014))
+-   修正错误 `count()` 结果 `SummingMergeTree` 当 `FINAL` 部分被使用。 [\#3280](https://github.com/ClickHouse/ClickHouse/issues/3280) [\#7786](https://github.com/ClickHouse/ClickHouse/pull/7786) ([尼基塔\*米哈伊洛夫](https://github.com/nikitamikhaylov))
+-   修复来自远程服务器的常量函数可能不正确的结果。 它发生在具有以下功能的查询中 `version()`, `uptime()` 等。 它为不同的服务器返回不同的常量值。 这修复 [\#7666](https://github.com/ClickHouse/ClickHouse/issues/7666). [\#7689](https://github.com/ClickHouse/ClickHouse/pull/7689) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   修复下推谓词优化中导致错误结果的复杂错误。 这解决了下推谓词优化的很多问题。 [\#8503](https://github.com/ClickHouse/ClickHouse/pull/8503) ([张冬](https://github.com/zhang2014))
+-   修复崩溃 `CREATE TABLE .. AS dictionary` 查询。 [\#8508](https://github.com/ClickHouse/ClickHouse/pull/8508) ([Azat Khuzhin](https://github.com/azat))
+-   一些改进ClickHouse语法 `.g4` 文件 [\#8294](https://github.com/ClickHouse/ClickHouse/pull/8294) ([太阳里](https://github.com/taiyang-li))
+-   修复导致崩溃的错误 `JOIN`s与表与发动机 `Join`. 这修复 [\#7556](https://github.com/ClickHouse/ClickHouse/issues/7556) [\#8254](https://github.com/ClickHouse/ClickHouse/issues/8254) [\#7915](https://github.com/ClickHouse/ClickHouse/issues/7915) [\#8100](https://github.com/ClickHouse/ClickHouse/issues/8100). [\#8298](https://github.com/ClickHouse/ClickHouse/pull/8298) ([Artem Zuikov](https://github.com/4ertus2))
+-   修复冗余字典重新加载 `CREATE DATABASE`. [\#7916](https://github.com/ClickHouse/ClickHouse/pull/7916) ([Azat Khuzhin](https://github.com/azat))
+-   限制从读取流的最大数量 `StorageFile` 和 `StorageHDFS`. 修复https://github.com/ClickHouse/ClickHouse/issues/7650. [\#7981](https://github.com/ClickHouse/ClickHouse/pull/7981) ([阿利沙平](https://github.com/alesapin))
+-   修复bug `ALTER ... MODIFY ... CODEC` 查询，当用户同时指定默认表达式和编解ec。 修复 [8593](https://github.com/ClickHouse/ClickHouse/issues/8593). [\#8614](https://github.com/ClickHouse/ClickHouse/pull/8614) ([阿利沙平](https://github.com/alesapin))
+-   修复列的后台合并错误 `SimpleAggregateFunction(LowCardinality)` 类型。 [\#8613](https://github.com/ClickHouse/ClickHouse/pull/8613) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   固定类型签入功能 `toDateTime64`. [\#8375](https://github.com/ClickHouse/ClickHouse/pull/8375) ([瓦西里\*内姆科夫](https://github.com/Enmk))
+-   现在服务器不崩溃 `LEFT` 或 `FULL JOIN` 与和加入引擎和不支持 `join_use_nulls` 设置。 [\#8479](https://github.com/ClickHouse/ClickHouse/pull/8479) ([Artem Zuikov](https://github.com/4ertus2))
+-   现在 `DROP DICTIONARY IF EXISTS db.dict` 查询不会抛出异常，如果 `db` 根本不存在 [\#8185](https://github.com/ClickHouse/ClickHouse/pull/8185) ([维塔利\*巴拉诺夫](https://github.com/vitlibar))
+-   修复表函数中可能出现的崩溃 (`file`, `mysql`, `remote`）引用删除引起的 `IStorage` 对象。 修复插入表函数时指定的列的不正确解析。 [\#7762](https://github.com/ClickHouse/ClickHouse/pull/7762) ([tavplubix](https://github.com/tavplubix))
+-   确保网络启动前 `clickhouse-server`. 这修复 [\#7507](https://github.com/ClickHouse/ClickHouse/issues/7507). [\#8570](https://github.com/ClickHouse/ClickHouse/pull/8570) ([余志昌](https://github.com/yuzhichang))
+-   修复安全连接的超时处理，因此查询不会无限挂起。 这修复 [\#8126](https://github.com/ClickHouse/ClickHouse/issues/8126). [\#8128](https://github.com/ClickHouse/ClickHouse/pull/8128) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复 `clickhouse-copier`并发工人之间的冗余争用。 [\#7816](https://github.com/ClickHouse/ClickHouse/pull/7816) ([丁香飞](https://github.com/dingxiangfei2009))
+-   现在突变不会跳过附加的部分，即使它们的突变版本比当前的突变版本大。 [\#7812](https://github.com/ClickHouse/ClickHouse/pull/7812) ([余志昌](https://github.com/yuzhichang)) [\#8250](https://github.com/ClickHouse/ClickHouse/pull/8250) ([阿利沙平](https://github.com/alesapin))
+-   忽略冗余副本 `*MergeTree` 数据部分移动到另一个磁盘和服务器重新启动后。 [\#7810](https://github.com/ClickHouse/ClickHouse/pull/7810) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   修复崩溃 `FULL JOIN` 与 `LowCardinality` 在 `JOIN` 钥匙 [\#8252](https://github.com/ClickHouse/ClickHouse/pull/8252) ([Artem Zuikov](https://github.com/4ertus2))
+-   禁止在插入查询中多次使用列名，如 `INSERT INTO tbl (x, y, x)`. 这修复 [\#5465](https://github.com/ClickHouse/ClickHouse/issues/5465), [\#7681](https://github.com/ClickHouse/ClickHouse/issues/7681). [\#7685](https://github.com/ClickHouse/ClickHouse/pull/7685) ([阿利沙平](https://github.com/alesapin))
+-   增加了回退，用于检测未知Cpu的物理CPU内核数量（使用逻辑CPU内核数量）。 这修复 [\#5239](https://github.com/ClickHouse/ClickHouse/issues/5239). [\#7726](https://github.com/ClickHouse/ClickHouse/pull/7726) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复 `There's no column` 实例化列和别名列出错。 [\#8210](https://github.com/ClickHouse/ClickHouse/pull/8210) ([Artem Zuikov](https://github.com/4ertus2))
+-   固定切断崩溃时 `EXISTS` 查询没有使用 `TABLE` 或 `DICTIONARY` 预选赛 就像 `EXISTS t`. 这修复 [\#8172](https://github.com/ClickHouse/ClickHouse/issues/8172). 此错误在版本19.17中引入。 [\#8213](https://github.com/ClickHouse/ClickHouse/pull/8213) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复罕见错误 `"Sizes of columns doesn't match"` 使用时可能会出现 `SimpleAggregateFunction` 列。 [\#7790](https://github.com/ClickHouse/ClickHouse/pull/7790) ([Boris Granveaud](https://github.com/bgranvea))
+-   修正错误，其中用户空 `allow_databases` 可以访问所有数据库（和相同的 `allow_dictionaries`). [\#7793](https://github.com/ClickHouse/ClickHouse/pull/7793) ([DeifyTheGod](https://github.com/DeifyTheGod))
+-   修复客户端崩溃时，服务器已经从客户端断开连接。 [\#8071](https://github.com/ClickHouse/ClickHouse/pull/8071) ([Azat Khuzhin](https://github.com/azat))
+-   修复 `ORDER BY` 在按主键前缀和非主键后缀排序的情况下的行为。 [\#7759](https://github.com/ClickHouse/ClickHouse/pull/7759) ([安东\*波波夫](https://github.com/CurtizJ))
+-   检查表中是否存在合格列。 这修复 [\#6836](https://github.com/ClickHouse/ClickHouse/issues/6836). [\#7758](https://github.com/ClickHouse/ClickHouse/pull/7758) ([Artem Zuikov](https://github.com/4ertus2))
+-   固定行为 `ALTER MOVE` 合并完成后立即运行移动指定的超部分。 修复 [\#8103](https://github.com/ClickHouse/ClickHouse/issues/8103). [\#8104](https://github.com/ClickHouse/ClickHouse/pull/8104) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   使用时修复可能的服务器崩溃 `UNION` 具有不同数量的列。 修复 [\#7279](https://github.com/ClickHouse/ClickHouse/issues/7279). [\#7929](https://github.com/ClickHouse/ClickHouse/pull/7929) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   修复函数结果子字符串的大小 `substr` 负大小。 [\#8589](https://github.com/ClickHouse/ClickHouse/pull/8589) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   现在服务器不执行部分突变 `MergeTree` 如果后台池中没有足够的可用线程。 [\#8588](https://github.com/ClickHouse/ClickHouse/pull/8588) ([tavplubix](https://github.com/tavplubix))
+-   修复格式化时的小错字 `UNION ALL` AST. [\#7999](https://github.com/ClickHouse/ClickHouse/pull/7999) ([litao91](https://github.com/litao91))
+-   修正了负数不正确的布隆过滤结果。 这修复 [\#8317](https://github.com/ClickHouse/ClickHouse/issues/8317). [\#8566](https://github.com/ClickHouse/ClickHouse/pull/8566) ([张冬](https://github.com/zhang2014))
+-   在解压缩固定潜在的缓冲区溢出。 恶意用户可以传递捏造的压缩数据，这将导致缓冲区后读取。 这个问题是由Yandex信息安全团队的Eldar Zaitov发现的。 [\#8404](https://github.com/ClickHouse/ClickHouse/pull/8404) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复因整数溢出而导致的错误结果 `arrayIntersect`. [\#7777](https://github.com/ClickHouse/ClickHouse/pull/7777) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   现在 `OPTIMIZE TABLE` query不会等待脱机副本执行该操作。 [\#8314](https://github.com/ClickHouse/ClickHouse/pull/8314) ([javi santana](https://github.com/javisantana))
+-   固定 `ALTER TTL` 解析器 `Replicated*MergeTree` 桌子 [\#8318](https://github.com/ClickHouse/ClickHouse/pull/8318) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   修复服务器和客户端之间的通信，以便服务器在查询失败后读取临时表信息。 [\#8084](https://github.com/ClickHouse/ClickHouse/pull/8084) ([Azat Khuzhin](https://github.com/azat))
+-   修复 `bitmapAnd` 在聚合位图和标量位图相交时出现函数错误。 [\#8082](https://github.com/ClickHouse/ClickHouse/pull/8082) ([黄月](https://github.com/moon03432))
+-   完善的定义 `ZXid` 根据动物园管理员的程序员指南，它修复了错误 `clickhouse-cluster-copier`. [\#8088](https://github.com/ClickHouse/ClickHouse/pull/8088) ([丁香飞](https://github.com/dingxiangfei2009))
+-   `odbc` 表函数现在尊重 `external_table_functions_use_nulls` 设置。 [\#7506](https://github.com/ClickHouse/ClickHouse/pull/7506) ([瓦西里\*内姆科夫](https://github.com/Enmk))
+-   修正了导致罕见的数据竞赛的错误。 [\#8143](https://github.com/ClickHouse/ClickHouse/pull/8143) ([亚历山大\*卡扎科夫](https://github.com/Akazz))
+-   现在 `SYSTEM RELOAD DICTIONARY` 完全重新加载字典，忽略 `update_field`. 这修复 [\#7440](https://github.com/ClickHouse/ClickHouse/issues/7440). [\#8037](https://github.com/ClickHouse/ClickHouse/pull/8037) ([维塔利\*巴拉诺夫](https://github.com/vitlibar))
+-   添加检查字典是否存在于创建查询的能力。 [\#8032](https://github.com/ClickHouse/ClickHouse/pull/8032) ([阿利沙平](https://github.com/alesapin))
+-   修复 `Float*` 解析中 `Values` 格式。 这修复 [\#7817](https://github.com/ClickHouse/ClickHouse/issues/7817). [\#7870](https://github.com/ClickHouse/ClickHouse/pull/7870) ([tavplubix](https://github.com/tavplubix))
+-   修复崩溃时，我们不能在一些后台操作保留空间 `*MergeTree` 表引擎家族. [\#7873](https://github.com/ClickHouse/ClickHouse/pull/7873) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   修复表包含合并操作时的崩溃 `SimpleAggregateFunction(LowCardinality)` 列。 这修复 [\#8515](https://github.com/ClickHouse/ClickHouse/issues/8515). [\#8522](https://github.com/ClickHouse/ClickHouse/pull/8522) ([Azat Khuzhin](https://github.com/azat))
+-   恢复对所有ICU区域设置的支持，并添加对常量表达式应用排序规则的功能。 还添加语言名称 `system.collations` 桌子 [\#8051](https://github.com/ClickHouse/ClickHouse/pull/8051) ([阿利沙平](https://github.com/alesapin))
+-   修正错误时，外部字典与零最小寿命 (`LIFETIME(MIN 0 MAX N)`, `LIFETIME(N)`）不要在后台更新。 [\#7983](https://github.com/ClickHouse/ClickHouse/pull/7983) ([阿利沙平](https://github.com/alesapin))
+-   修复当clickhouse源外部字典在查询中有子查询时崩溃。 [\#8351](https://github.com/ClickHouse/ClickHouse/pull/8351) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   修复文件扩展名不正确的解析表与引擎 `URL`. 这修复 [\#8157](https://github.com/ClickHouse/ClickHouse/issues/8157). [\#8419](https://github.com/ClickHouse/ClickHouse/pull/8419) ([安德烈\*博德罗夫](https://github.com/apbodrov))
+-   修复 `CHECK TABLE` 查询为 `*MergeTree` 表没有关键. 修复 [\#7543](https://github.com/ClickHouse/ClickHouse/issues/7543). [\#7979](https://github.com/ClickHouse/ClickHouse/pull/7979) ([阿利沙平](https://github.com/alesapin))
+-   固定转换 `Float64` 到MySQL类型。 [\#8079](https://github.com/ClickHouse/ClickHouse/pull/8079) ([尤里\*巴拉诺夫](https://github.com/yurriy))
+-   现在，如果表没有完全删除，因为服务器崩溃，服务器将尝试恢复并加载它。 [\#8176](https://github.com/ClickHouse/ClickHouse/pull/8176) ([tavplubix](https://github.com/tavplubix))
+-   修复了表函数中的崩溃 `file` 同时插入到不存在的文件。 现在在这种情况下，文件将被创建，然后插入将被处理。 [\#8177](https://github.com/ClickHouse/ClickHouse/pull/8177) ([Olga Khvostikova](https://github.com/stavrolia))
+-   修复罕见的死锁时，可能发生 `trace_log` 处于启用状态。 [\#7838](https://github.com/ClickHouse/ClickHouse/pull/7838) ([filimonov](https://github.com/filimonov))
+-   添加能力与不同类型的工作，除了 `Date` 在 `RangeHashed` 从DDL查询创建的外部字典。 修复 [7899](https://github.com/ClickHouse/ClickHouse/issues/7899). [\#8275](https://github.com/ClickHouse/ClickHouse/pull/8275) ([阿利沙平](https://github.com/alesapin))
+-   修复崩溃时 `now64()` 用另一个函数的结果调用。 [\#8270](https://github.com/ClickHouse/ClickHouse/pull/8270) ([瓦西里\*内姆科夫](https://github.com/Enmk))
+-   修正了通过mysql有线协议检测客户端IP连接的错误。 [\#7743](https://github.com/ClickHouse/ClickHouse/pull/7743) ([Dmitry Muzyka](https://github.com/dmitriy-myz))
+-   修复空阵列处理 `arraySplit` 功能。 这修复 [\#7708](https://github.com/ClickHouse/ClickHouse/issues/7708). [\#7747](https://github.com/ClickHouse/ClickHouse/pull/7747) ([hcz](https://github.com/hczhcz))
+-   修复了以下问题 `pid-file` 另一个运行 `clickhouse-server` 可能会被删除。 [\#8487](https://github.com/ClickHouse/ClickHouse/pull/8487) ([徐伟清](https://github.com/weiqxu))
+-   修复字典重新加载，如果它有 `invalidate_query`，停止更新，并在以前的更新尝试一些异常。 [\#8029](https://github.com/ClickHouse/ClickHouse/pull/8029) ([阿利沙平](https://github.com/alesapin))
+-   修正了功能错误 `arrayReduce` 这可能会导致 “double free” 和聚合函数组合器中的错误 `Resample` 这可能会导致内存泄漏。 添加聚合功能 `aggThrow`. 此功能可用于测试目的。 [\#8446](https://github.com/ClickHouse/ClickHouse/pull/8446) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+
+#### 改进 {#improvement-1}
+
+-   改进了使用时的日志记录 `S3` 表引擎。 [\#8251](https://github.com/ClickHouse/ClickHouse/pull/8251) ([Grigory Pervakov](https://github.com/GrigoryPervakov))
+-   在调用时未传递任何参数时打印帮助消息 `clickhouse-local`. 这修复 [\#5335](https://github.com/ClickHouse/ClickHouse/issues/5335). [\#8230](https://github.com/ClickHouse/ClickHouse/pull/8230) ([安德烈\*纳戈尔尼](https://github.com/Melancholic))
+-   添加设置 `mutations_sync` 这允许等待 `ALTER UPDATE/DELETE` 同步查询。 [\#8237](https://github.com/ClickHouse/ClickHouse/pull/8237) ([阿利沙平](https://github.com/alesapin))
+-   允许设置相对 `user_files_path` 在 `config.xml` （在类似的方式 `format_schema_path`). [\#7632](https://github.com/ClickHouse/ClickHouse/pull/7632) ([hcz](https://github.com/hczhcz))
+-   为转换函数添加非法类型的异常 `-OrZero` 后缀 [\#7880](https://github.com/ClickHouse/ClickHouse/pull/7880) ([安德烈\*科尼亚耶夫](https://github.com/akonyaev90))
+-   简化在分布式查询中发送到分片的数据头的格式。 [\#8044](https://github.com/ClickHouse/ClickHouse/pull/8044) ([维塔利\*巴拉诺夫](https://github.com/vitlibar))
+-   `Live View` 表引擎重构。 [\#8519](https://github.com/ClickHouse/ClickHouse/pull/8519) ([vzakaznikov](https://github.com/vzakaznikov))
+-   为从DDL查询创建的外部字典添加额外的检查。 [\#8127](https://github.com/ClickHouse/ClickHouse/pull/8127) ([阿利沙平](https://github.com/alesapin))
+-   修复错误 `Column ... already exists` 使用时 `FINAL` 和 `SAMPLE` together, e.g. `select count() from table final sample 1/2`. 修复 [\#5186](https://github.com/ClickHouse/ClickHouse/issues/5186). [\#7907](https://github.com/ClickHouse/ClickHouse/pull/7907) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   现在表的第一个参数 `joinGet` 函数可以是表标识符。 [\#7707](https://github.com/ClickHouse/ClickHouse/pull/7707) ([阿莫斯鸟](https://github.com/amosbird))
+-   允许使用 `MaterializedView` 与上面的子查询 `Kafka` 桌子 [\#8197](https://github.com/ClickHouse/ClickHouse/pull/8197) ([filimonov](https://github.com/filimonov))
+-   现在后台在磁盘之间移动，运行它的seprate线程池。 [\#7670](https://github.com/ClickHouse/ClickHouse/pull/7670) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   `SYSTEM RELOAD DICTIONARY` 现在同步执行。 [\#8240](https://github.com/ClickHouse/ClickHouse/pull/8240) ([维塔利\*巴拉诺夫](https://github.com/vitlibar))
+-   堆栈跟踪现在显示物理地址（对象文件中的偏移量），而不是虚拟内存地址（加载对象文件的位置）。 这允许使用 `addr2line` 当二进制独立于位置并且ASLR处于活动状态时。 这修复 [\#8360](https://github.com/ClickHouse/ClickHouse/issues/8360). [\#8387](https://github.com/ClickHouse/ClickHouse/pull/8387) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   支持行级安全筛选器的新语法: `<table name='table_name'>…</table>`. 修复 [\#5779](https://github.com/ClickHouse/ClickHouse/issues/5779). [\#8381](https://github.com/ClickHouse/ClickHouse/pull/8381) ([伊万](https://github.com/abyss7))
+-   现在 `cityHash` 功能可以与工作 `Decimal` 和 `UUID` 类型。 修复 [\#5184](https://github.com/ClickHouse/ClickHouse/issues/5184). [\#7693](https://github.com/ClickHouse/ClickHouse/pull/7693) ([米哈伊尔\*科罗托夫](https://github.com/millb))
+-   从系统日志中删除了固定的索引粒度（它是1024），因为它在实现自适应粒度之后已经过时。 [\#7698](https://github.com/ClickHouse/ClickHouse/pull/7698) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   当ClickHouse在没有SSL的情况下编译时，启用MySQL兼容服务器。 [\#7852](https://github.com/ClickHouse/ClickHouse/pull/7852) ([尤里\*巴拉诺夫](https://github.com/yurriy))
+-   现在服务器校验和分布式批处理，这在批处理中损坏数据的情况下提供了更多详细的错误。 [\#7914](https://github.com/ClickHouse/ClickHouse/pull/7914) ([Azat Khuzhin](https://github.com/azat))
+-   碌莽禄Support: `DROP DATABASE`, `DETACH TABLE`, `DROP TABLE` 和 `ATTACH TABLE` 为 `MySQL` 数据库引擎。 [\#8202](https://github.com/ClickHouse/ClickHouse/pull/8202) ([张冬](https://github.com/zhang2014))
+-   在S3表功能和表引擎中添加身份验证。 [\#7623](https://github.com/ClickHouse/ClickHouse/pull/7623) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   增加了检查额外的部分 `MergeTree` 在不同的磁盘上，为了不允许错过未定义磁盘上的数据部分。 [\#8118](https://github.com/ClickHouse/ClickHouse/pull/8118) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   启用Mac客户端和服务器的SSL支持。 [\#8297](https://github.com/ClickHouse/ClickHouse/pull/8297) ([伊万](https://github.com/abyss7))
+-   现在ClickHouse可以作为MySQL联合服务器（参见https://dev.mysql.com/doc/refman/5.7/en/federated-create-server.html）。 [\#7717](https://github.com/ClickHouse/ClickHouse/pull/7717) ([Maxim Fedotov](https://github.com/MaxFedotov))
+-   `clickhouse-client` 现在只能启用 `bracketed-paste` 当多查询处于打开状态且多行处于关闭状态时。 这修复（＃7757）\[https://github.com/ClickHouse/ClickHouse/issues/7757。 [\#7761](https://github.com/ClickHouse/ClickHouse/pull/7761) ([阿莫斯鸟](https://github.com/amosbird))
+-   碌莽禄Support: `Array(Decimal)` 在 `if` 功能。 [\#7721](https://github.com/ClickHouse/ClickHouse/pull/7721) ([Artem Zuikov](https://github.com/4ertus2))
+-   支持小数 `arrayDifference`, `arrayCumSum` 和 `arrayCumSumNegative` 功能。 [\#7724](https://github.com/ClickHouse/ClickHouse/pull/7724) ([Artem Zuikov](https://github.com/4ertus2))
+-   已添加 `lifetime` 列到 `system.dictionaries` 桌子 [\#6820](https://github.com/ClickHouse/ClickHouse/issues/6820) [\#7727](https://github.com/ClickHouse/ClickHouse/pull/7727) ([kekekekule](https://github.com/kekekekule))
+-   改进了检查不同磁盘上的现有部件 `*MergeTree` 表引擎. 地址 [\#7660](https://github.com/ClickHouse/ClickHouse/issues/7660). [\#8440](https://github.com/ClickHouse/ClickHouse/pull/8440) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   集成与 `AWS SDK` 为 `S3` 交互允许使用开箱即用的所有S3功能。 [\#8011](https://github.com/ClickHouse/ClickHouse/pull/8011) ([帕维尔\*科瓦连科](https://github.com/Jokser))
+-   增加了对子查询的支持 `Live View` 桌子 [\#7792](https://github.com/ClickHouse/ClickHouse/pull/7792) ([vzakaznikov](https://github.com/vzakaznikov))
+-   检查使用 `Date` 或 `DateTime` 从列 `TTL` 表达式已删除。 [\#7920](https://github.com/ClickHouse/ClickHouse/pull/7920) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   有关磁盘的信息已添加到 `system.detached_parts` 桌子 [\#7833](https://github.com/ClickHouse/ClickHouse/pull/7833) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   现在设置 `max_(table|partition)_size_to_drop` 无需重新启动即可更改。 [\#7779](https://github.com/ClickHouse/ClickHouse/pull/7779) ([Grigory Pervakov](https://github.com/GrigoryPervakov))
+-   错误消息的可用性略好。 要求用户不要删除下面的行 `Stack trace:`. [\#7897](https://github.com/ClickHouse/ClickHouse/pull/7897) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   更好地阅读消息 `Kafka` 引擎在各种格式后 [\#7935](https://github.com/ClickHouse/ClickHouse/issues/7935). [\#8035](https://github.com/ClickHouse/ClickHouse/pull/8035) ([伊万](https://github.com/abyss7))
+-   与不支持MySQL客户端更好的兼容性 `sha2_password` 验证插件。 [\#8036](https://github.com/ClickHouse/ClickHouse/pull/8036) ([尤里\*巴拉诺夫](https://github.com/yurriy))
+-   支持MySQL兼容性服务器中的更多列类型。 [\#7975](https://github.com/ClickHouse/ClickHouse/pull/7975) ([尤里\*巴拉诺夫](https://github.com/yurriy))
+-   执行 `ORDER BY` 优化 `Merge`, `Buffer` 和 `Materilized View` 存储与底层 `MergeTree` 桌子 [\#8130](https://github.com/ClickHouse/ClickHouse/pull/8130) ([安东\*波波夫](https://github.com/CurtizJ))
+-   现在我们总是使用POSIX实现 `getrandom` 与旧内核更好的兼容性（\<3.17）。 [\#7940](https://github.com/ClickHouse/ClickHouse/pull/7940) ([阿莫斯鸟](https://github.com/amosbird))
+-   更好地检查移动ttl规则中的有效目标。 [\#8410](https://github.com/ClickHouse/ClickHouse/pull/8410) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   更好地检查损坏的刀片批次 `Distributed` 表引擎。 [\#7933](https://github.com/ClickHouse/ClickHouse/pull/7933) ([Azat Khuzhin](https://github.com/azat))
+-   添加带有部件名称数组的列，这些部件将来必须处理突变 `system.mutations` 桌子 [\#8179](https://github.com/ClickHouse/ClickHouse/pull/8179) ([阿利沙平](https://github.com/alesapin))
+-   处理器的并行合并排序优化。 [\#8552](https://github.com/ClickHouse/ClickHouse/pull/8552) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   设置 `mark_cache_min_lifetime` 现在已经过时了，什么也不做。 在以前的版本中，标记缓存可以在内存中增长大于 `mark_cache_size` 以容纳内的数据 `mark_cache_min_lifetime` 秒。 这导致了混乱和比预期更高的内存使用率，这在内存受限的系统上尤其糟糕。 如果您在安装此版本后会看到性能下降，则应增加 `mark_cache_size`. [\#8484](https://github.com/ClickHouse/ClickHouse/pull/8484) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   准备使用 `tid` 到处都是 这是必要的 [\#7477](https://github.com/ClickHouse/ClickHouse/issues/7477). [\#8276](https://github.com/ClickHouse/ClickHouse/pull/8276) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+
+#### 性能改进 {#performance-improvement-1}
+
+-   处理器管道中的性能优化。 [\#7988](https://github.com/ClickHouse/ClickHouse/pull/7988) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   缓存字典中过期密钥的非阻塞更新（具有读取旧密钥的权限）。 [\#8303](https://github.com/ClickHouse/ClickHouse/pull/8303) ([尼基塔\*米哈伊洛夫](https://github.com/nikitamikhaylov))
+-   没有编译ClickHouse `-fno-omit-frame-pointer` 在全球范围内多余一个寄存器。 [\#8097](https://github.com/ClickHouse/ClickHouse/pull/8097) ([阿莫斯鸟](https://github.com/amosbird))
+-   加速 `greatCircleDistance` 功能，并为它添加性能测试。 [\#7307](https://github.com/ClickHouse/ClickHouse/pull/7307) ([Olga Khvostikova](https://github.com/stavrolia))
+-   改进的功能性能 `roundDown`. [\#8465](https://github.com/ClickHouse/ClickHouse/pull/8465) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   改进的性能 `max`, `min`, `argMin`, `argMax` 为 `DateTime64` 数据类型。 [\#8199](https://github.com/ClickHouse/ClickHouse/pull/8199) ([瓦西里\*内姆科夫](https://github.com/Enmk))
+-   改进了无限制或大限制和外部排序的排序性能。 [\#8545](https://github.com/ClickHouse/ClickHouse/pull/8545) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   改进的性能格式化浮点数高达6倍。 [\#8542](https://github.com/ClickHouse/ClickHouse/pull/8542) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   改进的性能 `modulo` 功能。 [\#7750](https://github.com/ClickHouse/ClickHouse/pull/7750) ([阿莫斯鸟](https://github.com/amosbird))
+-   优化 `ORDER BY` 并与单列键合并。 [\#8335](https://github.com/ClickHouse/ClickHouse/pull/8335) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   更好地实施 `arrayReduce`, `-Array` 和 `-State` 组合子 [\#7710](https://github.com/ClickHouse/ClickHouse/pull/7710) ([阿莫斯鸟](https://github.com/amosbird))
+-   现在 `PREWHERE` 应优化为至少一样高效 `WHERE`. [\#7769](https://github.com/ClickHouse/ClickHouse/pull/7769) ([阿莫斯鸟](https://github.com/amosbird))
+-   改进方式 `round` 和 `roundBankers` 处理负数。 [\#8229](https://github.com/ClickHouse/ClickHouse/pull/8229) ([hcz](https://github.com/hczhcz))
+-   改进的解码性能 `DoubleDelta` 和 `Gorilla` 编解码器大约30-40％。 这修复 [\#7082](https://github.com/ClickHouse/ClickHouse/issues/7082). [\#8019](https://github.com/ClickHouse/ClickHouse/pull/8019) ([瓦西里\*内姆科夫](https://github.com/Enmk))
+-   改进的性能 `base64` 相关功能。 [\#8444](https://github.com/ClickHouse/ClickHouse/pull/8444) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   增加了一个功能 `geoDistance`. 它类似于 `greatCircleDistance` 但使用近似于WGS-84椭球模型。 两个功能的性能几乎相同。 [\#8086](https://github.com/ClickHouse/ClickHouse/pull/8086) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   更快 `min` 和 `max` 聚合函数 `Decimal` 数据类型。 [\#8144](https://github.com/ClickHouse/ClickHouse/pull/8144) ([Artem Zuikov](https://github.com/4ertus2))
+-   矢量化处理 `arrayReduce`. [\#7608](https://github.com/ClickHouse/ClickHouse/pull/7608) ([阿莫斯鸟](https://github.com/amosbird))
+-   `if` 链现在优化为 `multiIf`. [\#8355](https://github.com/ClickHouse/ClickHouse/pull/8355) ([kamalov-ruslan](https://github.com/kamalov-ruslan))
+-   修复性能回归 `Kafka` 表引擎在19.15中引入。 这修复 [\#7261](https://github.com/ClickHouse/ClickHouse/issues/7261). [\#7935](https://github.com/ClickHouse/ClickHouse/pull/7935) ([filimonov](https://github.com/filimonov))
+-   已删除 “pie” 代码生成 `gcc` 从Debian软件包偶尔带来默认情况下。 [\#8483](https://github.com/ClickHouse/ClickHouse/pull/8483) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   并行解析数据格式 [\#6553](https://github.com/ClickHouse/ClickHouse/pull/6553) ([尼基塔\*米哈伊洛夫](https://github.com/nikitamikhaylov))
+-   启用优化的解析器 `Values` 默认使用表达式 (`input_format_values_deduce_templates_of_expressions=1`). [\#8231](https://github.com/ClickHouse/ClickHouse/pull/8231) ([tavplubix](https://github.com/tavplubix))
+
+#### 构建/测试/包装改进 {#buildtestingpackaging-improvement-2}
+
+-   构建修复 `ARM` 而在最小模式。 [\#8304](https://github.com/ClickHouse/ClickHouse/pull/8304) ([proller](https://github.com/proller))
+-   添加复盖文件刷新 `clickhouse-server` 当不调用std::atexit时。 还略微改进了无状态测试的复盖率日志记录。 [\#8267](https://github.com/ClickHouse/ClickHouse/pull/8267) ([阿利沙平](https://github.com/alesapin))
+-   更新contrib中的LLVM库。 避免从操作系统包中使用LLVM。 [\#8258](https://github.com/ClickHouse/ClickHouse/pull/8258) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   使bund绑 `curl` 建立完全安静。 [\#8232](https://github.com/ClickHouse/ClickHouse/pull/8232) [\#8203](https://github.com/ClickHouse/ClickHouse/pull/8203) ([帕维尔\*科瓦连科](https://github.com/Jokser))
+-   修复一些 `MemorySanitizer` 警告。 [\#8235](https://github.com/ClickHouse/ClickHouse/pull/8235) ([Alexander Kuzmenkov](https://github.com/akuzm))
+-   使用 `add_warning` 和 `no_warning` 宏 `CMakeLists.txt`. [\#8604](https://github.com/ClickHouse/ClickHouse/pull/8604) ([伊万](https://github.com/abyss7))
+-   添加对Minio S3兼容对象的支持（https://min.io/)为了更好的集成测试。 [\#7863](https://github.com/ClickHouse/ClickHouse/pull/7863) [\#7875](https://github.com/ClickHouse/ClickHouse/pull/7875) ([帕维尔\*科瓦连科](https://github.com/Jokser))
+-   导入 `libc` 标题到contrib。 它允许在各种系统中使构建更加一致（仅适用于 `x86_64-linux-gnu`). [\#5773](https://github.com/ClickHouse/ClickHouse/pull/5773) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   删除 `-fPIC` 从一些图书馆。 [\#8464](https://github.com/ClickHouse/ClickHouse/pull/8464) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   清洁 `CMakeLists.txt` 对于卷曲。 看https://github.com/ClickHouse/ClickHouse/pull/8011\#issuecomment-569478910 [\#8459](https://github.com/ClickHouse/ClickHouse/pull/8459) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   无声警告 `CapNProto` 图书馆. [\#8220](https://github.com/ClickHouse/ClickHouse/pull/8220) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   为短字符串优化哈希表添加性能测试。 [\#7679](https://github.com/ClickHouse/ClickHouse/pull/7679) ([阿莫斯鸟](https://github.com/amosbird))
+-   现在ClickHouse将建立在 `AArch64` 即使 `MADV_FREE` 不可用。 这修复 [\#8027](https://github.com/ClickHouse/ClickHouse/issues/8027). [\#8243](https://github.com/ClickHouse/ClickHouse/pull/8243) ([阿莫斯鸟](https://github.com/amosbird))
+-   更新 `zlib-ng` 来解决记忆消毒的问题 [\#7182](https://github.com/ClickHouse/ClickHouse/pull/7182) [\#8206](https://github.com/ClickHouse/ClickHouse/pull/8206) ([Alexander Kuzmenkov](https://github.com/akuzm))
+-   在非Linux系统上启用内部MySQL库，因为操作系统包的使用非常脆弱，通常根本不起作用。 这修复 [\#5765](https://github.com/ClickHouse/ClickHouse/issues/5765). [\#8426](https://github.com/ClickHouse/ClickHouse/pull/8426) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复了启用后在某些系统上构建的问题 `libc++`. 这取代了 [\#8374](https://github.com/ClickHouse/ClickHouse/issues/8374). [\#8380](https://github.com/ClickHouse/ClickHouse/pull/8380) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   赂眉露\>\> `Field` 方法更类型安全，以找到更多的错误。 [\#7386](https://github.com/ClickHouse/ClickHouse/pull/7386) [\#8209](https://github.com/ClickHouse/ClickHouse/pull/8209) ([Alexander Kuzmenkov](https://github.com/akuzm))
+-   添加丢失的文件到 `libc-headers` 子模块。 [\#8507](https://github.com/ClickHouse/ClickHouse/pull/8507) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复错误 `JSON` 引用性能测试输出。 [\#8497](https://github.com/ClickHouse/ClickHouse/pull/8497) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   现在堆栈跟踪显示 `std::exception` 和 `Poco::Exception`. 在以前的版本中，它仅适用于 `DB::Exception`. 这改进了诊断。 [\#8501](https://github.com/ClickHouse/ClickHouse/pull/8501) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   移植 `clock_gettime` 和 `clock_nanosleep` 对于新鲜的glibc版本。 [\#8054](https://github.com/ClickHouse/ClickHouse/pull/8054) ([阿莫斯鸟](https://github.com/amosbird))
+-   启用 `part_log` 在示例配置开发人员。 [\#8609](https://github.com/ClickHouse/ClickHouse/pull/8609) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复重新加载的异步性质 `01036_no_superfluous_dict_reload_on_create_database*`. [\#8111](https://github.com/ClickHouse/ClickHouse/pull/8111) ([Azat Khuzhin](https://github.com/azat))
+-   固定编解码器性能测试。 [\#8615](https://github.com/ClickHouse/ClickHouse/pull/8615) ([瓦西里\*内姆科夫](https://github.com/Enmk))
+-   添加安装脚本 `.tgz` 为他们构建和文档。 [\#8612](https://github.com/ClickHouse/ClickHouse/pull/8612) [\#8591](https://github.com/ClickHouse/ClickHouse/pull/8591) ([阿利沙平](https://github.com/alesapin))
+-   删除旧 `ZSTD` 测试（它是在2016年创建的，以重现zstd1.0版本之前的错误）。 这修复 [\#8618](https://github.com/ClickHouse/ClickHouse/issues/8618). [\#8619](https://github.com/ClickHouse/ClickHouse/pull/8619) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   固定构建在Mac OS卡特琳娜。 [\#8600](https://github.com/ClickHouse/ClickHouse/pull/8600) ([meo](https://github.com/meob))
+-   增加编解码器性能测试中的行数，以使结果显着。 [\#8574](https://github.com/ClickHouse/ClickHouse/pull/8574) ([瓦西里\*内姆科夫](https://github.com/Enmk))
+-   在调试版本中，处理 `LOGICAL_ERROR` 异常作为断言失败，使得它们更容易被注意到。 [\#8475](https://github.com/ClickHouse/ClickHouse/pull/8475) ([Alexander Kuzmenkov](https://github.com/akuzm))
+-   使与格式相关的性能测试更具确定性。 [\#8477](https://github.com/ClickHouse/ClickHouse/pull/8477) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   更新 `lz4` 来修复记忆消毒器的故障 [\#8181](https://github.com/ClickHouse/ClickHouse/pull/8181) ([Alexander Kuzmenkov](https://github.com/akuzm))
+-   在异常处理中抑制已知MemorySanitizer误报。 [\#8182](https://github.com/ClickHouse/ClickHouse/pull/8182) ([Alexander Kuzmenkov](https://github.com/akuzm))
+-   更新 `gcc` 和 `g++` 到版本9在 `build/docker/build.sh` [\#7766](https://github.com/ClickHouse/ClickHouse/pull/7766) ([TLightSky](https://github.com/tlightsky))
+-   添加性能测试用例来测试 `PREWHERE` 比 `WHERE`. [\#7768](https://github.com/ClickHouse/ClickHouse/pull/7768) ([阿莫斯鸟](https://github.com/amosbird))
+-   在修复一个笨拙的测试方面取得了进展。 [\#8621](https://github.com/ClickHouse/ClickHouse/pull/8621) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   避免从MemorySanitizer报告数据 `libunwind`. [\#8539](https://github.com/ClickHouse/ClickHouse/pull/8539) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   更新 `libc++` 到最新版本。 [\#8324](https://github.com/ClickHouse/ClickHouse/pull/8324) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   从源头构建ICU库。 这修复 [\#6460](https://github.com/ClickHouse/ClickHouse/issues/6460). [\#8219](https://github.com/ClickHouse/ClickHouse/pull/8219) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   从切换 `libressl` 到 `openssl`. ClickHouse应在此更改后支持TLS1.3和SNI。 这修复 [\#8171](https://github.com/ClickHouse/ClickHouse/issues/8171). [\#8218](https://github.com/ClickHouse/ClickHouse/pull/8218) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   使用时固定的UBSan报告 `chacha20_poly1305` 从SSL（发生在连接到https://yandex.ru/)。 [\#8214](https://github.com/ClickHouse/ClickHouse/pull/8214) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复默认密码文件的模式 `.deb` linux发行版。 [\#8075](https://github.com/ClickHouse/ClickHouse/pull/8075) ([proller](https://github.com/proller))
+-   改进的表达式获取 `clickhouse-server` PID输入 `clickhouse-test`. [\#8063](https://github.com/ClickHouse/ClickHouse/pull/8063) ([亚历山大\*卡扎科夫](https://github.com/Akazz))
+-   更新contrib/googletest到v1.10.0。 [\#8587](https://github.com/ClickHouse/ClickHouse/pull/8587) ([Alexander Burmak](https://github.com/Alex-Burmak))
+-   修复了ThreadSaninitizer报告 `base64` 图书馆. 还将此库更新到最新版本，但无关紧要。 这修复 [\#8397](https://github.com/ClickHouse/ClickHouse/issues/8397). [\#8403](https://github.com/ClickHouse/ClickHouse/pull/8403) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   修复 `00600_replace_running_query` 对于处理器。 [\#8272](https://github.com/ClickHouse/ClickHouse/pull/8272) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   删除支持 `tcmalloc` 为了使 `CMakeLists.txt` 更简单 [\#8310](https://github.com/ClickHouse/ClickHouse/pull/8310) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   发布海湾合作委员会构建现在使用 `libc++` 而不是 `libstdc++`. 最近 `libc++` 只与叮当一起使用。 这将提高构建配置的一致性和可移植性。 [\#8311](https://github.com/ClickHouse/ClickHouse/pull/8311) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   使用MemorySanitizer启用ICU库进行构建。 [\#8222](https://github.com/ClickHouse/ClickHouse/pull/8222) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   禁止从警告 `CapNProto` 图书馆. [\#8224](https://github.com/ClickHouse/ClickHouse/pull/8224) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   删除代码的特殊情况 `tcmalloc`，因为它不再受支持。 [\#8225](https://github.com/ClickHouse/ClickHouse/pull/8225) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   在CI coverage任务中，优雅地终止服务器以允许它保存coverage报告。 这修复了我们最近看到的不完整的复盖率报告。 [\#8142](https://github.com/ClickHouse/ClickHouse/pull/8142) ([阿利沙平](https://github.com/alesapin))
+-   针对所有编解码器的性能测试 `Float64` 和 `UInt64` 值。 [\#8349](https://github.com/ClickHouse/ClickHouse/pull/8349) ([瓦西里\*内姆科夫](https://github.com/Enmk))
+-   `termcap` 非常不推荐使用，并导致各种问题（f.g.missing “up” 帽和呼应 `^J` 而不是多行）。 帮个忙 `terminfo` 或bund绑 `ncurses`. [\#7737](https://github.com/ClickHouse/ClickHouse/pull/7737) ([阿莫斯鸟](https://github.com/amosbird))
+-   修复 `test_storage_s3` 集成测试。 [\#7734](https://github.com/ClickHouse/ClickHouse/pull/7734) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   碌莽禄Support: `StorageFile(<format>, null)` 将块插入给定格式的文件而不实际写入磁盘。 这是性能测试所必需的。 [\#8455](https://github.com/ClickHouse/ClickHouse/pull/8455) ([阿莫斯鸟](https://github.com/amosbird))
+-   添加参数 `--print-time` 功能测试打印每个测试的执行时间。 [\#8001](https://github.com/ClickHouse/ClickHouse/pull/8001) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   添加断言 `KeyCondition` 同时评估RPN。 这将修复来自gcc-9的警告。 [\#8279](https://github.com/ClickHouse/ClickHouse/pull/8279) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   在CI构建中转储cmake选项。 [\#8273](https://github.com/ClickHouse/ClickHouse/pull/8273) ([Alexander Kuzmenkov](https://github.com/akuzm))
+-   不要为某些fat库生成调试信息。 [\#8271](https://github.com/ClickHouse/ClickHouse/pull/8271) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   赂眉露\>\> `log_to_console.xml` 始终登录到stderr，无论它是否交互。 [\#8395](https://github.com/ClickHouse/ClickHouse/pull/8395) ([Alexander Kuzmenkov](https://github.com/akuzm))
+-   删除了一些未使用的功能 `clickhouse-performance-test` 工具 [\#8555](https://github.com/ClickHouse/ClickHouse/pull/8555) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   现在我们也将搜索 `lld-X` 与相应的 `clang-X` 版本。 [\#8092](https://github.com/ClickHouse/ClickHouse/pull/8092) ([阿利沙平](https://github.com/alesapin))
+-   实木复合地板建设改善。 [\#8421](https://github.com/ClickHouse/ClickHouse/pull/8421) ([马苏兰](https://github.com/maxulan))
+-   更多海湾合作委员会警告 [\#8221](https://github.com/ClickHouse/ClickHouse/pull/8221) ([kreuzerkrieg](https://github.com/kreuzerkrieg))
+-   Arch Linux的软件包现在允许运行ClickHouse服务器，而不仅仅是客户端。 [\#8534](https://github.com/ClickHouse/ClickHouse/pull/8534) ([Vladimir Chebotarev](https://github.com/excitoon))
+-   修复与处理器的测试。 微小的性能修复。 [\#7672](https://github.com/ClickHouse/ClickHouse/pull/7672) ([尼古拉\*科切托夫](https://github.com/KochetovNicolai))
+-   更新contrib/protobuf。 [\#8256](https://github.com/ClickHouse/ClickHouse/pull/8256) ([Matwey V.Kornilov](https://github.com/matwey))
+-   在准备切换到c++20作为新年庆祝活动。 “May the C++ force be with ClickHouse.” [\#8447](https://github.com/ClickHouse/ClickHouse/pull/8447) ([阿莫斯鸟](https://github.com/amosbird))
+
+#### 实验特点 {#experimental-feature-1}
+
+-   增加了实验设置 `min_bytes_to_use_mmap_io`. 它允许读取大文件，而无需将数据从内核复制到用户空间。 默认情况下禁用该设置。 建议的阈值大约是64MB，因为mmap/munmap很慢。 [\#8520](https://github.com/ClickHouse/ClickHouse/pull/8520) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+-   返工配额作为访问控制系统的一部分。 增加了新表 `system.quotas`，新功能 `currentQuota`, `currentQuotaKey`，新的SQL语法 `CREATE QUOTA`, `ALTER QUOTA`, `DROP QUOTA`, `SHOW QUOTA`. [\#7257](https://github.com/ClickHouse/ClickHouse/pull/7257) ([维塔利\*巴拉诺夫](https://github.com/vitlibar))
+-   允许跳过带有警告的未知设置，而不是引发异常。 [\#7653](https://github.com/ClickHouse/ClickHouse/pull/7653) ([维塔利\*巴拉诺夫](https://github.com/vitlibar))
+-   重新设计的行策略作为访问控制系统的一部分。 增加了新表 `system.row_policies`，新功能 `currentRowPolicies()`，新的SQL语法 `CREATE POLICY`, `ALTER POLICY`, `DROP POLICY`, `SHOW CREATE POLICY`, `SHOW POLICIES`. [\#7808](https://github.com/ClickHouse/ClickHouse/pull/7808) ([维塔利\*巴拉诺夫](https://github.com/vitlibar))
+
+#### 安全修复 {#security-fix}
+
+-   修正了读取目录结构中的表的可能性 `File` 表引擎。 这修复 [\#8536](https://github.com/ClickHouse/ClickHouse/issues/8536). [\#8537](https://github.com/ClickHouse/ClickHouse/pull/8537) ([阿列克谢-米洛维多夫](https://github.com/alexey-milovidov))
+
+## [更新日志2019](https://github.com/ClickHouse/ClickHouse/blob/master/docs/en/changelog/2019.md) {#changelog-for-2019}

docs/zh/commercial/cloud.md

@@ -1,20 +1,21 @@
 ---
-en_copy: true
+machine_translated: true
+machine_translated_rev: b111334d6614a02564cf32f379679e9ff970d9b1
 ---
 
-# ClickHouse Cloud Service Providers {#clickhouse-cloud-service-providers}
+# ﾂ环板Providersｮﾂ嘉ｯ {#clickhouse-cloud-service-providers}
 
-!!! info "Info"
-    If you have launched a public cloud with managed ClickHouse service, feel free to [open a pull-request](https://github.com/ClickHouse/ClickHouse/edit/master/docs/en/commercial/cloud.md) adding it to the following list.
+!!! info "信息"
+    如果您已经启动了带有托管ClickHouse服务的公共云，请随时 [打开拉取请求](https://github.com/ClickHouse/ClickHouse/edit/master/docs/en/commercial/cloud.md) 将其添加到以下列表。
 
-## Yandex Cloud {#yandex-cloud}
+## Yandex云 {#yandex-cloud}
 
-[Yandex Managed Service for ClickHouse](https://cloud.yandex.com/services/managed-clickhouse?utm_source=referrals&utm_medium=clickhouseofficialsite&utm_campaign=link3) provides the following key features:
+[Yandex的ClickHouse托管服务](https://cloud.yandex.com/services/managed-clickhouse?utm_source=referrals&utm_medium=clickhouseofficialsite&utm_campaign=link3) 提供以下主要功能:
 
--   Fully managed ZooKeeper service for [ClickHouse replication](../operations/table_engines/replication.md)
--   Multiple storage type choices
--   Replicas in different availability zones
--   Encryption and isolation
--   Automated maintenance
+-   全面管理的动物园管理员服务 [ClickHouse复制](../engines/table_engines/mergetree_family/replication.md)
+-   多种存储类型选择
+-   不同可用区中的副本
+-   加密和隔离
+-   自动化维护
 
-{## [Original article](https://clickhouse.tech/docs/en/commercial/cloud/) ##}
+{## [原始文章](https://clickhouse.tech/docs/en/commercial/cloud/) ##}

docs/zh/commercial/index.md

@@ -0,0 +1,9 @@
+---
+machine_translated: true
+machine_translated_rev: b111334d6614a02564cf32f379679e9ff970d9b1
+toc_folder_title: "\u5546\u4E1A"
+toc_priority: 70
+toc_title: "\u5546\u4E1A"
+---
+
+

docs/zh/data_types/datetime64.md

@@ -1,101 +0,0 @@
----
-en_copy: true
----
-
-# DateTime64 {#data_type-datetime64}
-
-Allows to store an instant in time, that can be expressed as a calendar date and a time of a day, with defined sub-second precision
-
-Tick size (precision): 10<sup>-precision</sup> seconds
-
-Syntax:
-
-``` sql
-DateTime64(precision, [timezone])
-```
-
-Internally, stores data as a number of ‘ticks’ since epoch start (1970-01-01 00:00:00 UTC) as Int64. The tick resolution is determined by the precision parameter. Additionally, the `DateTime64` type can store time zone that is the same for the entire column, that affects how the values of the `DateTime64` type values are displayed in text format and how the values specified as strings are parsed (‘2020-01-01 05:00:01.000’). The time zone is not stored in the rows of the table (or in resultset), but is stored in the column metadata. See details in [DateTime](datetime.md).
-
-## Examples {#examples}
-
-**1.** Creating a table with `DateTime64`-type column and inserting data into it:
-
-``` sql
-CREATE TABLE dt
-(
-    `timestamp` DateTime64(3, 'Europe/Moscow'),
-    `event_id` UInt8
-)
-ENGINE = TinyLog
-```
-
-``` sql
-INSERT INTO dt Values (1546300800000, 1), ('2019-01-01 00:00:00', 2)
-```
-
-``` sql
-SELECT * FROM dt
-```
-
-``` text
-┌───────────────timestamp─┬─event_id─┐
-│ 2019-01-01 03:00:00.000 │        1 │
-│ 2019-01-01 00:00:00.000 │        2 │
-└─────────────────────────┴──────────┘
-```
-
--   When inserting datetime as an integer, it is treated as an appropriately scaled Unix Timestamp (UTC). `1546300800000` (with precision 3) represents `'2019-01-01 00:00:00'` UTC. However, as `timestamp` column has `Europe/Moscow` (UTC+3) timezone specified, when outputting as a string the value will be shown as `'2019-01-01 03:00:00'`
--   When inserting string value as datetime, it is treated as being in column timezone. `'2019-01-01 00:00:00'` will be treated as being in `Europe/Moscow` timezone and stored as `1546290000000`.
-
-**2.** Filtering on `DateTime64` values
-
-``` sql
-SELECT * FROM dt WHERE timestamp = toDateTime64('2019-01-01 00:00:00', 3, 'Europe/Moscow')
-```
-
-``` text
-┌───────────────timestamp─┬─event_id─┐
-│ 2019-01-01 00:00:00.000 │        2 │
-└─────────────────────────┴──────────┘
-```
-
-Unlike `DateTime`, `DateTime64` values are not converted from `String` automatically
-
-**3.** Getting a time zone for a `DateTime64`-type value:
-
-``` sql
-SELECT toDateTime64(now(), 3, 'Europe/Moscow') AS column, toTypeName(column) AS x
-```
-
-``` text
-┌──────────────────column─┬─x──────────────────────────────┐
-│ 2019-10-16 04:12:04.000 │ DateTime64(3, 'Europe/Moscow') │
-└─────────────────────────┴────────────────────────────────┘
-```
-
-**4.** Timezone conversion
-
-``` sql
-SELECT
-toDateTime64(timestamp, 3, 'Europe/London') as lon_time,
-toDateTime64(timestamp, 3, 'Europe/Moscow') as mos_time
-FROM dt
-```
-
-``` text
-┌───────────────lon_time──┬────────────────mos_time─┐
-│ 2019-01-01 00:00:00.000 │ 2019-01-01 03:00:00.000 │
-│ 2018-12-31 21:00:00.000 │ 2019-01-01 00:00:00.000 │
-└─────────────────────────┴─────────────────────────┘
-```
-
-## See Also {#see-also}
-
--   [Type conversion functions](../query_language/functions/type_conversion_functions.md)
--   [Functions for working with dates and times](../query_language/functions/date_time_functions.md)
--   [Functions for working with arrays](../query_language/functions/array_functions.md)
--   [The `date_time_input_format` setting](../operations/settings/settings.md#settings-date_time_input_format)
--   [The `timezone` server configuration parameter](../operations/server_settings/settings.md#server_settings-timezone)
--   [Operators for working with dates and times](../query_language/operators.md#operators-datetime)
--   [`Date` data type](date.md)
--   [`DateTime` data type](datetime.md)

docs/zh/data_types/int_uint.md

@@ -1,17 +0,0 @@
-# UInt8, UInt16, UInt32, UInt64, Int8, Int16, Int32, Int64 {#uint8-uint16-uint32-uint64-int8-int16-int32-int64}
-
-固定长度的整型，包括有符号整型或无符号整型。
-
-## 整型范围 {#zheng-xing-fan-wei}
-
--   Int8 - \[-128 : 127\]
--   Int16 - \[-32768 : 32767\]
--   Int32 - \[-2147483648 : 2147483647\]
--   Int64 - \[-9223372036854775808 : 9223372036854775807\]
-
-## 无符号整型范围 {#wu-fu-hao-zheng-xing-fan-wei}
-
--   UInt8 - \[0 : 255\]
--   UInt16 - \[0 : 65535\]
--   UInt32 - \[0 : 4294967295\]
--   UInt64 - \[0 : 18446744073709551615\]

docs/zh/data_types/uuid.md

@@ -1,74 +0,0 @@
----
-en_copy: true
----
-
-# UUID {#uuid-data-type}
-
-A universally unique identifier (UUID) is a 16-byte number used to identify records. For detailed information about the UUID, see [Wikipedia](https://en.wikipedia.org/wiki/Universally_unique_identifier).
-
-The example of UUID type value is represented below:
-
-``` text
-61f0c404-5cb3-11e7-907b-a6006ad3dba0
-```
-
-If you do not specify the UUID column value when inserting a new record, the UUID value is filled with zero:
-
-``` text
-00000000-0000-0000-0000-000000000000
-```
-
-## How to generate {#how-to-generate}
-
-To generate the UUID value, ClickHouse provides the [generateUUIDv4](../query_language/functions/uuid_functions.md) function.
-
-## Usage example {#usage-example}
-
-**Example 1**
-
-This example demonstrates creating a table with the UUID type column and inserting a value into the table.
-
-``` sql
-CREATE TABLE t_uuid (x UUID, y String) ENGINE=TinyLog
-```
-
-``` sql
-INSERT INTO t_uuid SELECT generateUUIDv4(), 'Example 1'
-```
-
-``` sql
-SELECT * FROM t_uuid
-```
-
-``` text
-┌────────────────────────────────────x─┬─y─────────┐
-│ 417ddc5d-e556-4d27-95dd-a34d84e46a50 │ Example 1 │
-└──────────────────────────────────────┴───────────┘
-```
-
-**Example 2**
-
-In this example, the UUID column value is not specified when inserting a new record.
-
-``` sql
-INSERT INTO t_uuid (y) VALUES ('Example 2')
-```
-
-``` sql
-SELECT * FROM t_uuid
-```
-
-``` text
-┌────────────────────────────────────x─┬─y─────────┐
-│ 417ddc5d-e556-4d27-95dd-a34d84e46a50 │ Example 1 │
-│ 00000000-0000-0000-0000-000000000000 │ Example 2 │
-└──────────────────────────────────────┴───────────┘
-```
-
-## Restrictions {#restrictions}
-
-The UUID data type only supports functions which [String](string.md) data type also supports (for example, [min](../query_language/agg_functions/reference.md#agg_function-min), [max](../query_language/agg_functions/reference.md#agg_function-max), and [count](../query_language/agg_functions/reference.md#agg_function-count)).
-
-The UUID data type is not supported by arithmetic operations (for example, [abs](../query_language/functions/arithmetic_functions.md#arithm_func-abs)) or aggregate functions, such as [sum](../query_language/agg_functions/reference.md#agg_function-sum) and [avg](../query_language/agg_functions/reference.md#agg_function-avg).
-
-[Original article](https://clickhouse.tech/docs/en/data_types/uuid/) <!--hide-->

docs/zh/database_engines/lazy.md

@@ -1,15 +0,0 @@
----
-en_copy: true
----
-
-# Lazy {#lazy}
-
-Keeps tables in RAM only `expiration_time_in_seconds` seconds after last access. Can be used only with \*Log tables.
-
-It’s optimized for storing many small \*Log tables, for which there is a long time interval between accesses.
-
-## Creating a Database {#creating-a-database}
-
-    CREATE DATABASE testlazy ENGINE = Lazy(expiration_time_in_seconds);
-
-[Original article](https://clickhouse.tech/docs/en/database_engines/lazy/) <!--hide-->

docs/zh/development/architecture.md

@@ -1,3 +1,4 @@
+
 # ClickHouse 架构概述 {#clickhouse-jia-gou-gai-shu}
 
 ClickHouse 是一个真正的列式数据库管理系统（DBMS)。在 ClickHouse 中，数据始终是按列存储的，包括矢量（向量或列块）执行的过程。只要有可能，操作都是基于矢量进行分派的，而不是单个的值，这被称为«矢量化查询执行»，它有利于降低实际的数据处理开销。
@@ -12,7 +13,7 @@ ClickHouse 是一个真正的列式数据库管理系统（DBMS)。在 ClickHous
 
 不同的 `IColumn` 实现（`ColumnUInt8`、`ColumnString` 等）负责不同的列内存布局。内存布局通常是一个连续的数组。对于数据类型为整型的列，只是一个连续的数组，比如 `std::vector`。对于 `String` 列和 `Array` 列，则由两个向量组成：其中一个向量连续存储所有的 `String` 或数组元素，另一个存储每一个 `String` 或 `Array` 的起始元素在第一个向量中的偏移。而 `ColumnConst` 则仅在内存中存储一个值，但是看起来像一个列。
 
-## Field {#field}
+## 字段 {#field}
 
 尽管如此，有时候也可能需要处理单个值。表示单个值，可以使用 `Field`。`Field` 是 `UInt64`、`Int64`、`Float64`、`String` 和 `Array` 组成的联合。`IColumn` 拥有 `operator[]` 方法来获取第 `n` 个值成为一个 `Field`，同时也拥有 `insert` 方法将一个 `Field` 追加到一个列的末尾。这些方法并不高效，因为它们需要处理表示单一值的临时 `Field` 对象，但是有更高效的方法比如 `insertFrom` 和 `insertRangeFrom` 等。
 
@@ -115,7 +116,7 @@ ClickHouse 是一个真正的列式数据库管理系统（DBMS)。在 ClickHous
 
 普通函数不会改变行数 - 它们的执行看起来就像是独立地处理每一行数据。实际上，函数不会作用于一个单独的行上，而是作用在以 `Block` 为单位的数据上，以实现向量查询执行。
 
-还有一些杂项函数，比如 [blockSize](../query_language/functions/other_functions.md#function-blocksize)、[rowNumberInBlock](../query_language/functions/other_functions.md#function-rownumberinblock)，以及 [runningAccumulate](../query_language/functions/other_functions.md#function-runningaccumulate)，它们对块进行处理，并且不遵从行的独立性。
+还有一些杂项函数，比如 [块大小](../sql_reference/functions/other_functions.md#function-blocksize)、[rowNumberInBlock](../sql_reference/functions/other_functions.md#function-rownumberinblock)，以及 [跑累积](../sql_reference/functions/other_functions.md#function-runningaccumulate)，它们对块进行处理，并且不遵从行的独立性。
 
 ClickHouse 具有强类型，因此隐式类型转换不会发生。如果函数不支持某个特定的类型组合，则会抛出异常。但函数可以通过重载以支持许多不同的类型组合。比如，`plus` 函数（用于实现 `+` 运算符）支持任意数字类型的组合：`UInt8` + `Float32`，`UInt16` + `Int8` 等。同时，一些可变参数的函数能够级接收任意数目的参数，比如 `concat` 函数。
 
@@ -159,7 +160,7 @@ ClickHouse 具有强类型，因此隐式类型转换不会发生。如果函数
 
 分布式查询执行没有全局查询计划。每个节点都有针对自己的工作部分的本地查询计划。我们仅有简单的一次性分布式查询执行：将查询发送给远程节点，然后合并结果。但是对于具有高基数的 `GROUP BY` 或具有大量临时数据的 `JOIN` 这样困难的查询的来说，这是不可行的：在这种情况下，我们需要在服务器之间«改组»数据，这需要额外的协调。ClickHouse 不支持这类查询执行，我们需要在这方面进行努力。
 
-## Merge Tree {#merge-tree}
+## 合并树 {#merge-tree}
 
 `MergeTree` 是一系列支持按主键索引的存储引擎。主键可以是一个任意的列或表达式的元组。`MergeTree` 表中的数据存储于«分块»中。每一个分块以主键序存储数据（数据按主键元组的字典序排序）。表的所有列都存储在这些«分块»中分离的 `column.bin` 文件中。`column.bin` 文件由压缩块组成，每一个块通常是 64 KB 到 1 MB 大小的未压缩数据，具体取决于平均值大小。这些块由一个接一个连续放置的列值组成。每一列的列值顺序相同（顺序由主键定义），因此当你按多列进行迭代时，你能够得到相应列的值。
 

docs/zh/development/browse_code.md

@@ -1,11 +1,14 @@
 ---
-en_copy: true
+machine_translated: true
+machine_translated_rev: b111334d6614a02564cf32f379679e9ff970d9b1
+toc_priority: 63
+toc_title: "\u6D4F\u89C8ClickHouse\u6E90\u4EE3\u7801"
 ---
 
-# Browse ClickHouse Source Code {#browse-clickhouse-source-code}
+# 浏览ClickHouse源代码 {#browse-clickhouse-source-code}
 
-You can use **Woboq** online code browser available [here](https://clickhouse-test-reports.s3.yandex.net/codebrowser/html_report///ClickHouse/dbms/index.html). It provides code navigation and semantic highlighting, search and indexing. The code snapshot is updated daily.
+您可以使用 **Woboq** 在线代码浏览器可用 [这里](https://clickhouse-test-reports.s3.yandex.net/codebrowser/html_report///ClickHouse/src/index.html). 它提供了代码导航和语义突出显示，搜索和索引。 代码快照每天更新。
 
-Also, you can browse sources on [GitHub](https://github.com/ClickHouse/ClickHouse) as usual.
+此外，您还可以浏览源 [GitHub](https://github.com/ClickHouse/ClickHouse) 像往常一样
 
-If you’re interested what IDE to use, we recommend CLion, QT Creator, VS Code and KDevelop (with caveats). You can use any favourite IDE. Vim and Emacs also count.
+如果你有兴趣使用什么样的IDE，我们建议CLion，QT Creator，VS Code和KDevelop（有注意事项）。 您可以使用任何喜欢的IDE。 Vim和Emacs也算数。

docs/zh/development/build.md

@@ -1,3 +1,4 @@
+
 # 如何构建 ClickHouse 发布包 {#ru-he-gou-jian-clickhouse-fa-bu-bao}
 
 ## 安装 Git 和 Pbuilder {#an-zhuang-git-he-pbuilder}
@@ -32,12 +33,12 @@ cd ClickHouse
 sudo apt-get install git cmake ninja-build
 ```
 
-Or cmake3 instead of cmake on older systems.
+或cmake3而不是旧系统上的cmake。
 或者在早期版本的系统中用 cmake3 替代 cmake
 
 ## 安装 GCC 9 {#an-zhuang-gcc-9}
 
-There are several ways to do this.
+有几种方法可以做到这一点。
 
 ### 安装 PPA 包 {#an-zhuang-ppa-bao}
 
@@ -79,6 +80,6 @@ cd ..
 ```
 
 若要创建一个执行文件， 执行 `ninja clickhouse`。
-这个命令会使得 `programs/clickhouse` 文件可执行，您可以使用 `client` or `server` 参数运行。
+这个命令会使得 `programs/clickhouse` 文件可执行，您可以使用 `client` 或 `server` 参数运行。
 
 [来源文章](https://clickhouse.tech/docs/en/development/build/) <!--hide-->

docs/zh/development/build_cross_arm.md

@@ -1,17 +1,21 @@
 ---
-en_copy: true
+machine_translated: true
+machine_translated_rev: b111334d6614a02564cf32f379679e9ff970d9b1
+toc_priority: 67
+toc_title: "\u5982\u4F55\u5728Linux\u4E0A\u6784\u5EFAClickHouse for AARCH64\uFF08\
+  ARM64)"
 ---
 
-# How to Build ClickHouse on Linux for AARCH64 (ARM64) architecture {#how-to-build-clickhouse-on-linux-for-aarch64-arm64-architecture}
+# 如何在Linux上为AARCH64（ARM64）架构构建ClickHouse {#how-to-build-clickhouse-on-linux-for-aarch64-arm64-architecture}
 
-This is for the case when you have Linux machine and want to use it to build `clickhouse` binary that will run on another Linux machine with AARCH64 CPU architecture. This is intended for continuous integration checks that run on Linux servers.
+这是当你有Linux机器，并希望使用它来构建的情况下 `clickhouse` 二进制文件将运行在另一个Linux机器上与AARCH64CPU架构。 这适用于在Linux服务器上运行的持续集成检查。
 
-The cross-build for AARCH64 is based on the [Build instructions](build.md), follow them first.
+Aarch64的交叉构建基于 [构建说明](build.md) 先跟着他们
 
-# Install Clang-8 {#install-clang-8}
+# 安装Clang-8 {#install-clang-8}
 
-Follow the instructions from https://apt.llvm.org/ for your Ubuntu or Debian setup.
-For example, in Ubuntu Bionic you can use the following commands:
+按照以下说明操作https://apt.llvm.org/为您的Ubuntu或Debian设置.
+例如，在Ubuntu Bionic中，您可以使用以下命令:
 
 ``` bash
 echo "deb [trusted=yes] http://apt.llvm.org/bionic/ llvm-toolchain-bionic-8 main" | sudo tee /etc/apt/sources.list.d/llvm.list
@@ -19,7 +23,7 @@ sudo apt-get update
 sudo apt-get install clang-8
 ```
 
-# Install Cross-Compilation Toolset {#install-cross-compilation-toolset}
+# 安装交叉编译工具集 {#install-cross-compilation-toolset}
 
 ``` bash
 cd ClickHouse
@@ -28,7 +32,7 @@ wget 'https://developer.arm.com/-/media/Files/downloads/gnu-a/8.3-2019.03/binrel
 tar xJf gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu.tar.xz -C build-aarch64/cmake/toolchain/linux-aarch64 --strip-components=1
 ```
 
-# Build ClickHouse {#build-clickhouse}
+# 建立ClickHouse {#build-clickhouse}
 
 ``` bash
 cd ClickHouse
@@ -37,4 +41,4 @@ CC=clang-8 CXX=clang++-8 cmake . -Bbuild-arm64 -DCMAKE_TOOLCHAIN_FILE=cmake/linu
 ninja -C build-arm64
 ```
 
-The resulting binary will run only on Linux with the AARCH64 CPU architecture.
+生成的二进制文件将仅在具有AARCH64CPU体系结构的Linux上运行。

docs/zh/development/build_cross_osx.md

@@ -1,10 +1,11 @@
+
 # 如何在Linux中编译Mac OS X ClickHouse {#ru-he-zai-linuxzhong-bian-yi-mac-os-x-clickhouse}
 
 Linux机器也可以编译运行在OS X系统的`clickhouse`二进制包，这可以用于在Linux上跑持续集成测试。如果要在Mac OS X上直接构建ClickHouse，请参考另外一篇指南： https://clickhouse.tech/docs/zh/development/build\_osx/
 
 Mac OS X的交叉编译基于以下构建说明，请首先遵循它们。
 
-# Install Clang-8 {#install-clang-8}
+# 安装Clang-8 {#install-clang-8}
 
 按照https://apt.llvm.org/中的说明进行Ubuntu或Debian安装。
 例如，安装Bionic的命令如下：

docs/zh/development/build_osx.md

@@ -1,3 +1,4 @@
+
 # 在 Mac OS X 中编译 ClickHouse {#zai-mac-os-x-zhong-bian-yi-clickhouse}
 
 ClickHouse 支持在 Mac OS X 10.12 版本中编译。若您在用更早的操作系统版本，可以尝试在指令中使用 `Gentoo Prefix` 和 `clang sl`.
@@ -43,7 +44,7 @@ cd ..
 
 为此，请创建以下文件：
 
-/Library/LaunchDaemons/limit.maxfiles.plist:
+/图书馆/LaunchDaemons/限制.maxfilesplist:
 
 ``` xml
 <?xml version="1.0" encoding="UTF-8"?>

docs/zh/development/contrib.md

@@ -1,34 +1,35 @@
+
 # 使用的三方库 {#shi-yong-de-san-fang-ku}
 
-| Library             | License                                                                                                                                      |
-|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
-| base64              | [BSD 2-Clause License](https://github.com/aklomp/base64/blob/a27c565d1b6c676beaf297fe503c4518185666f7/LICENSE)                               |
-| boost               | [Boost Software License 1.0](https://github.com/ClickHouse-Extras/boost-extra/blob/6883b40449f378019aec792f9983ce3afc7ff16e/LICENSE_1_0.txt) |
-| brotli              | [MIT](https://github.com/google/brotli/blob/master/LICENSE)                                                                                  |
-| capnproto           | [MIT](https://github.com/capnproto/capnproto/blob/master/LICENSE)                                                                            |
-| cctz                | [Apache License 2.0](https://github.com/google/cctz/blob/4f9776a310f4952454636363def82c2bf6641d5f/LICENSE.txt)                               |
-| double-conversion   | [BSD 3-Clause License](https://github.com/google/double-conversion/blob/cf2f0f3d547dc73b4612028a155b80536902ba02/LICENSE)                    |
-| FastMemcpy          | [MIT](https://github.com/ClickHouse/ClickHouse/blob/master/libs/libmemcpy/impl/LICENSE)                                                      |
-| googletest          | [BSD 3-Clause License](https://github.com/google/googletest/blob/master/LICENSE)                                                             |
-| hyperscan           | [BSD 3-Clause License](https://github.com/intel/hyperscan/blob/master/LICENSE)                                                               |
-| libbtrie            | [BSD 2-Clause License](https://github.com/ClickHouse/ClickHouse/blob/master/contrib/libbtrie/LICENSE)                                        |
-| libcxxabi           | [BSD + MIT](https://github.com/ClickHouse/ClickHouse/blob/master/libs/libglibc-compatibility/libcxxabi/LICENSE.TXT)                          |
-| libdivide           | [Zlib License](https://github.com/ClickHouse/ClickHouse/blob/master/contrib/libdivide/LICENSE.txt)                                           |
-| libgsasl            | [LGPL v2.1](https://github.com/ClickHouse-Extras/libgsasl/blob/3b8948a4042e34fb00b4fb987535dc9e02e39040/LICENSE)                             |
-| libhdfs3            | [Apache License 2.0](https://github.com/ClickHouse-Extras/libhdfs3/blob/bd6505cbb0c130b0db695305b9a38546fa880e5a/LICENSE.txt)                |
-| libmetrohash        | [Apache License 2.0](https://github.com/ClickHouse/ClickHouse/blob/master/contrib/libmetrohash/LICENSE)                                      |
-| libpcg-random       | [Apache License 2.0](https://github.com/ClickHouse/ClickHouse/blob/master/contrib/libpcg-random/LICENSE-APACHE.txt)                          |
-| libressl            | [OpenSSL License](https://github.com/ClickHouse-Extras/ssl/blob/master/COPYING)                                                              |
-| librdkafka          | [BSD 2-Clause License](https://github.com/edenhill/librdkafka/blob/363dcad5a23dc29381cc626620e68ae418b3af19/LICENSE)                         |
-| libwidechar\_width  | [CC0 1.0 Universal](https://github.com/ClickHouse/ClickHouse/blob/master/libs/libwidechar_width/LICENSE)                                     |
-| llvm                | [BSD 3-Clause License](https://github.com/ClickHouse-Extras/llvm/blob/163def217817c90fb982a6daf384744d8472b92b/llvm/LICENSE.TXT)             |
-| lz4                 | [BSD 2-Clause License](https://github.com/lz4/lz4/blob/c10863b98e1503af90616ae99725ecd120265dfb/LICENSE)                                     |
-| mariadb-connector-c | [LGPL v2.1](https://github.com/ClickHouse-Extras/mariadb-connector-c/blob/3.1/COPYING.LIB)                                                   |
-| murmurhash          | [Public Domain](https://github.com/ClickHouse/ClickHouse/blob/master/contrib/murmurhash/LICENSE)                                             |
-| pdqsort             | [Zlib License](https://github.com/ClickHouse/ClickHouse/blob/master/contrib/pdqsort/license.txt)                                             |
-| poco                | [Boost Software License - Version 1.0](https://github.com/ClickHouse-Extras/poco/blob/fe5505e56c27b6ecb0dcbc40c49dc2caf4e9637f/LICENSE)      |
-| protobuf            | [BSD 3-Clause License](https://github.com/ClickHouse-Extras/protobuf/blob/12735370922a35f03999afff478e1c6d7aa917a4/LICENSE)                  |
-| re2                 | [BSD 3-Clause License](https://github.com/google/re2/blob/7cf8b88e8f70f97fd4926b56aa87e7f53b2717e0/LICENSE)                                  |
-| UnixODBC            | [LGPL v2.1](https://github.com/ClickHouse-Extras/UnixODBC/tree/b0ad30f7f6289c12b76f04bfb9d466374bb32168)                                     |
-| zlib-ng             | [Zlib License](https://github.com/ClickHouse-Extras/zlib-ng/blob/develop/LICENSE.md)                                                         |
-| zstd                | [BSD 3-Clause License](https://github.com/facebook/zstd/blob/dev/LICENSE)                                                                    |
+| 图书馆             | 许可                                                                                                                                |
+|--------------------|-------------------------------------------------------------------------------------------------------------------------------------|
+| base64             | [BSD2-条款许可](https://github.com/aklomp/base64/blob/a27c565d1b6c676beaf297fe503c4518185666f7/LICENSE)                             |
+| 升压               | [提升软件许可证1.0](https://github.com/ClickHouse-Extras/boost-extra/blob/6883b40449f378019aec792f9983ce3afc7ff16e/LICENSE_1_0.txt) |
+| brotli             | [MIT](https://github.com/google/brotli/blob/master/LICENSE)                                                                         |
+| capnproto          | [MIT](https://github.com/capnproto/capnproto/blob/master/LICENSE)                                                                   |
+| cctz               | [Apache许可证2.0](https://github.com/google/cctz/blob/4f9776a310f4952454636363def82c2bf6641d5f/LICENSE.txt)                         |
+| 双转换             | [BSD3-条款许可](https://github.com/google/double-conversion/blob/cf2f0f3d547dc73b4612028a155b80536902ba02/LICENSE)                  |
+| FastMemcpy         | [MIT](https://github.com/ClickHouse/ClickHouse/blob/master/libs/libmemcpy/impl/LICENSE)                                             |
+| googletest         | [BSD3-条款许可](https://github.com/google/googletest/blob/master/LICENSE)                                                           |
+| 超扫描             | [BSD3-条款许可](https://github.com/intel/hyperscan/blob/master/LICENSE)                                                             |
+| libbtrie           | [BSD2-条款许可](https://github.com/ClickHouse/ClickHouse/blob/master/contrib/libbtrie/LICENSE)                                      |
+| libcxxabi          | [BSD + MIT](https://github.com/ClickHouse/ClickHouse/blob/master/libs/libglibc-compatibility/libcxxabi/LICENSE.TXT)                 |
+| libdivide          | [Zlib许可证](https://github.com/ClickHouse/ClickHouse/blob/master/contrib/libdivide/LICENSE.txt)                                    |
+| libgsasl           | [LGPL v2.1](https://github.com/ClickHouse-Extras/libgsasl/blob/3b8948a4042e34fb00b4fb987535dc9e02e39040/LICENSE)                    |
+| libhdfs3           | [Apache许可证2.0](https://github.com/ClickHouse-Extras/libhdfs3/blob/bd6505cbb0c130b0db695305b9a38546fa880e5a/LICENSE.txt)          |
+| libmetrohash       | [Apache许可证2.0](https://github.com/ClickHouse/ClickHouse/blob/master/contrib/libmetrohash/LICENSE)                                |
+| libpcg-随机        | [Apache许可证2.0](https://github.com/ClickHouse/ClickHouse/blob/master/contrib/libpcg-random/LICENSE-APACHE.txt)                    |
+| libressl           | [OpenSSL许可证](https://github.com/ClickHouse-Extras/ssl/blob/master/COPYING)                                                       |
+| librdkafka         | [BSD2-条款许可](https://github.com/edenhill/librdkafka/blob/363dcad5a23dc29381cc626620e68ae418b3af19/LICENSE)                       |
+| libwidechar\_width | [CC0 1.0通用](https://github.com/ClickHouse/ClickHouse/blob/master/libs/libwidechar_width/LICENSE)                                  |
+| llvm               | [BSD3-条款许可](https://github.com/ClickHouse-Extras/llvm/blob/163def217817c90fb982a6daf384744d8472b92b/llvm/LICENSE.TXT)           |
+| lz4                | [BSD2-条款许可](https://github.com/lz4/lz4/blob/c10863b98e1503af90616ae99725ecd120265dfb/LICENSE)                                   |
+| mariadb-连接器-c   | [LGPL v2.1](https://github.com/ClickHouse-Extras/mariadb-connector-c/blob/3.1/COPYING.LIB)                                          |
+| murmurhash         | [公共领域](https://github.com/ClickHouse/ClickHouse/blob/master/contrib/murmurhash/LICENSE)                                         |
+| pdqsort            | [Zlib许可证](https://github.com/ClickHouse/ClickHouse/blob/master/contrib/pdqsort/license.txt)                                      |
+| poco               | [提升软件许可证-1.0版](https://github.com/ClickHouse-Extras/poco/blob/fe5505e56c27b6ecb0dcbc40c49dc2caf4e9637f/LICENSE)             |
+| protobuf           | [BSD3-条款许可](https://github.com/ClickHouse-Extras/protobuf/blob/12735370922a35f03999afff478e1c6d7aa917a4/LICENSE)                |
+| re2                | [BSD3-条款许可](https://github.com/google/re2/blob/7cf8b88e8f70f97fd4926b56aa87e7f53b2717e0/LICENSE)                                |
+| UnixODBC           | [LGPL v2.1](https://github.com/ClickHouse-Extras/UnixODBC/tree/b0ad30f7f6289c12b76f04bfb9d466374bb32168)                            |
+| zlib-ng            | [Zlib许可证](https://github.com/ClickHouse-Extras/zlib-ng/blob/develop/LICENSE.md)                                                  |
+| zstd               | [BSD3-条款许可](https://github.com/facebook/zstd/blob/dev/LICENSE)                                                                  |

docs/zh/development/developer_instruction.md

@@ -1,3 +1,4 @@
+
 ClickHose支持Linux,FreeBSD 及 Mac OS X 系统。
 
 # Windows使用指引 {#windowsshi-yong-zhi-yin}
@@ -67,9 +68,9 @@ ClickHose支持Linux,FreeBSD 及 Mac OS X 系统。
 
 命令执行成功后，可以通过执行`git pull upstream master`，从ClickHouse的主分支中拉去更新。
 
-## Working with submodules {#working-with-submodules}
+## 使用子模块 {#working-with-submodules}
 
-Working with submodules in git could be painful. Next commands will help to manage it:
+在git中使用子模块可能会很痛苦。 接下来的命令将有助于管理它:
 
     # ! each command accepts --recursive
     # Update remote URLs for submodules. Barely rare case
@@ -81,7 +82,7 @@ Working with submodules in git could be painful. Next commands will help to mana
     # Two last commands could be merged together
     git submodule update --init
 
-The next commands would help you to reset all submodules to the initial state (!WARING! - any chenges inside will be deleted):
+接下来的命令将帮助您将所有子模块重置为初始状态（！华林！ -里面的任何chenges将被删除):
 
     # Synchronizes submodules' remote URL with .gitmodules
     git submodule sync --recursive

docs/zh/development/index.md

@@ -1,3 +1,4 @@
+
 # ClickHouse 开发 {#clickhouse-kai-fa}
 
 [来源文章](https://clickhouse.tech/docs/en/development/) <!--hide-->

docs/zh/development/style.md

@@ -1,3 +1,4 @@
+
 # 如何编写 C++ 代码 {#ru-he-bian-xie-c-dai-ma}
 
 ## 一般建议 {#yi-ban-jian-yi}
@@ -200,7 +201,7 @@ std::cerr << static_cast<int>(c) << std::endl;
 for (Names::const_iterator it = column_names.begin(); it != column_names.end(); ++it)
 ```
 
-## Comments {#comments}
+## 评论 {#comments}
 
 **1.** 请务必为所有非常重要的代码部分添加注释。
 
@@ -297,7 +298,7 @@ void executeQuery(
 /// for
 ```
 
-## Names {#names}
+## 姓名 {#names}
 
 **1.** 在变量和类成员的名称中使用带下划线的小写字母。
 
@@ -623,7 +624,7 @@ Loader() {}
 
 **18.** 编码。
 
-在所有情况下使用 UTF-8 编码。使用 `std::string` and `char *`。不要使用 `std::wstring` 和 `wchar_t`。
+在所有情况下使用 UTF-8 编码。使用 `std::string` 和 `char *`。不要使用 `std::wstring` 和 `wchar_t`。
 
 **19.** 日志。
 

docs/zh/development/tests.md

@@ -1,3 +1,4 @@
+
 # ClickHouse 测试 {#clickhouse-ce-shi}
 
 ## 功能性测试 {#gong-neng-xing-ce-shi}
@@ -14,7 +15,7 @@
 
 调用功能测试最简单的方法是将 `clickhouse-client` 复制到`/usr/bin/`，运行`clickhouse-server`，然后从自己的目录运行`./ clickhouse-test`。
 
-要添加新测试，请在 `tests/queries/0_stateless` 目录内添加新的 `.sql` 或 `.sh` 文件，手动检查，然后按以下方式生成 `.reference` 文件： `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` or `./00000_test.sh > ./00000_test.reference`。
+要添加新测试，请在 `tests/queries/0_stateless` 目录内添加新的 `.sql` 或 `.sh` 文件，手动检查，然后按以下方式生成 `.reference` 文件： `clickhouse-client -n --testmode < 00000_test.sql > 00000_test.reference` 或 `./00000_test.sh > ./00000_test.reference`。
 
 测试应该只使用（创建，删除等）`test` 数据库中的表，这些表假定是事先创建的; 测试也可以使用临时表。
 
@@ -152,24 +153,24 @@ Clang 有更多有用的警告 - 您可以使用 `-Weverything` 查找它们并
 
 对于生产构建，使用 gcc（它仍然生成比 clang 稍高效的代码）。对于开发来说，clang 通常更方便使用。您可以使用调试模式在自己的机器上构建（以节省笔记本电脑的电量），但请注意，由于更好的控制流程和过程分析，编译器使用 `-O3` 会生成更多警告。 当使用 clang 构建时，使用 `libc++` 而不是 `libstdc++`，并且在使用调试模式构建时，使用调试版本的 `libc++`，它允许在运行时捕获更多错误。
 
-## Sanitizers {#sanitizers}
+## 消毒剂 {#sanitizers}
 
-**Address sanitizer**.
+**地址消毒剂**.
 我们在每个提交的基础上在 ASan 下运行功能和集成测试。
 
-**Valgrind (Memcheck)**.
+**ﾂ暗ｪﾂ氾环催ﾂ団ﾂ法ﾂ人)**.
 我们在 Valgrind 过夜进行功能测试。 这需要几个小时。 目前在 `re2` 库中有一个已知的误报，请参阅 [文章](https://research.swtch.com/sparse)。
 
-**Thread sanitizer**.
+**螺纹消毒剂**.
 我们在 TSan 下进行功能测试。ClickHouse 必须通过所有测试。在 TSan 下运行不是自动化的，只是偶尔执行。
 
-**Memory sanitizer**.
+**记忆消毒剂**.
 目前我们不使用 MSan。
 
-**Undefined behaviour sanitizer.**
+**未定义的行为消毒剂。**
 我们仍然不会在每次提交的基础上使用 UBSan。 有一些地方需要解决。
 
-**Debug allocator.**
+**调试分alloc。**
 您可以使用 `DEBUG_TCMALLOC` CMake 选项启用 `tcmalloc` 的调试版本。我们在每次提交的基础上使用调试分配器运行测试。
 
 更多请参阅 `tests/instructions/sanitizers.txt`。

docs/zh/engines/database_engines/index.md

@@ -1,8 +1,9 @@
+
 # 数据库引擎 {#shu-ju-ku-yin-qing}
 
 您使用的所有表都是由数据库引擎所提供的
 
-默认情况下，ClickHouse使用自己的数据库引擎，该引擎提供可配置的[表引擎](../operations/table_engines/index.md)和[所有支持的SQL语法](../query_language/syntax.md).
+默认情况下，ClickHouse使用自己的数据库引擎，该引擎提供可配置的[表引擎](../../engines/database_engines/index.md)和[所有支持的SQL语法](../../engines/database_engines/index.md).
 
 除此之外，您还可以选择使用以下的数据库引擎：
 

docs/zh/engines/database_engines/lazy.md

@@ -0,0 +1,18 @@
+---
+machine_translated: true
+machine_translated_rev: b111334d6614a02564cf32f379679e9ff970d9b1
+toc_priority: 31
+toc_title: "\u61D2\u60F0"
+---
+
+# 懒惰 {#lazy}
+
+仅将表保留在RAM中 `expiration_time_in_seconds` 上次访问后几秒钟。 只能与\*日志表一起使用。
+
+它针对存储许多小\*日志表进行了优化，访问之间存在较长的时间间隔。
+
+## 创建数据库 {#creating-a-database}
+
+    CREATE DATABASE testlazy ENGINE = Lazy(expiration_time_in_seconds);
+
+[原始文章](https://clickhouse.tech/docs/en/database_engines/lazy/) <!--hide-->

docs/zh/engines/database_engines/mysql.md

@@ -1,3 +1,4 @@
+
 # MySQL {#mysql}
 
 MySQL引擎用于将远程的MySQL服务器中的表映射到ClickHouse中，并允许您对表进行`INSERT`和`SELECT`查询，以方便您在ClickHouse与MySQL之间进行数据交换。
@@ -6,8 +7,6 @@ MySQL引擎用于将远程的MySQL服务器中的表映射到ClickHouse中，并
 
 但您无法对其执行以下操作：
 
--   `ATTACH`/`DETACH`
--   `DROP`
 -   `RENAME`
 -   `CREATE TABLE`
 -   `ALTER`
@@ -16,7 +15,7 @@ MySQL引擎用于将远程的MySQL服务器中的表映射到ClickHouse中，并
 
 ``` sql
 CREATE DATABASE [IF NOT EXISTS] db_name [ON CLUSTER cluster]
-ENGINE = MySQL('host:port', 'database', 'user', 'password')
+ENGINE = MySQL('host:port', ['database' | database], 'user', 'password')
 ```
 
 **MySQL数据库引擎参数**
@@ -28,25 +27,25 @@ ENGINE = MySQL('host:port', 'database', 'user', 'password')
 
 ## 支持的类型对应 {#zhi-chi-de-lei-xing-dui-ying}
 
-| MySQL                            | ClickHouse                                  |
-|----------------------------------|---------------------------------------------|
-| UNSIGNED TINYINT                 | [UInt8](../data_types/int_uint.md)          |
-| TINYINT                          | [Int8](../data_types/int_uint.md)           |
-| UNSIGNED SMALLINT                | [UInt16](../data_types/int_uint.md)         |
-| SMALLINT                         | [Int16](../data_types/int_uint.md)          |
-| UNSIGNED INT, UNSIGNED MEDIUMINT | [UInt32](../data_types/int_uint.md)         |
-| INT, MEDIUMINT                   | [Int32](../data_types/int_uint.md)          |
-| UNSIGNED BIGINT                  | [UInt64](../data_types/int_uint.md)         |
-| BIGINT                           | [Int64](../data_types/int_uint.md)          |
-| FLOAT                            | [Float32](../data_types/float.md)           |
-| DOUBLE                           | [Float64](../data_types/float.md)           |
-| DATE                             | [Date](../data_types/date.md)               |
-| DATETIME, TIMESTAMP              | [DateTime](../data_types/datetime.md)       |
-| BINARY                           | [FixedString](../data_types/fixedstring.md) |
+| MySQL                            | ClickHouse                                                  |
+|----------------------------------|-------------------------------------------------------------|
+| UNSIGNED TINYINT                 | [UInt8](../../sql_reference/data_types/int_uint.md)         |
+| TINYINT                          | [Int8](../../sql_reference/data_types/int_uint.md)          |
+| UNSIGNED SMALLINT                | [UInt16](../../sql_reference/data_types/int_uint.md)        |
+| SMALLINT                         | [Int16](../../sql_reference/data_types/int_uint.md)         |
+| UNSIGNED INT, UNSIGNED MEDIUMINT | [UInt32](../../sql_reference/data_types/int_uint.md)        |
+| INT, MEDIUMINT                   | [Int32](../../sql_reference/data_types/int_uint.md)         |
+| UNSIGNED BIGINT                  | [UInt64](../../sql_reference/data_types/int_uint.md)        |
+| BIGINT                           | [Int64](../../sql_reference/data_types/int_uint.md)         |
+| FLOAT                            | [Float32](../../sql_reference/data_types/float.md)          |
+| DOUBLE                           | [Float64](../../sql_reference/data_types/float.md)          |
+| DATE                             | [日期](../../sql_reference/data_types/date.md)              |
+| DATETIME, TIMESTAMP              | [日期时间](../../sql_reference/data_types/datetime.md)      |
+| BINARY                           | [固定字符串](../../sql_reference/data_types/fixedstring.md) |
 
-其他的MySQL数据类型将全部都转换为[String](../data_types/string.md)。
+其他的MySQL数据类型将全部都转换为[字符串](../../sql_reference/data_types/string.md)。
 
-同时以上的所有类型都支持[Nullable](../data_types/nullable.md)。
+同时以上的所有类型都支持[可为空](../../sql_reference/data_types/nullable.md)。
 
 ## 使用示例 {#shi-yong-shi-li}
 

docs/zh/engines/index.md

@@ -0,0 +1,8 @@
+---
+machine_translated: true
+machine_translated_rev: b111334d6614a02564cf32f379679e9ff970d9b1
+toc_folder_title: "\u53D1\u52A8\u673A"
+toc_priority: 25
+---
+
+

docs/zh/engines/table_engines/index.md

@@ -1,3 +1,4 @@
+
 # 表引擎 {#biao-yin-qing}
 
 表引擎（即表的类型）决定了：
@@ -13,54 +14,54 @@
 
 ## MergeTree {#mergetree}
 
-适用于高负载任务的最通用和功能最强大的表引擎。这些引擎的共同特点是可以快速插入数据并进行后续的后台数据处理。 MergeTree系列引擎支持数据复制（使用[Replicated\*](replication.md) 的引擎版本），分区和一些其他引擎不支持的其他功能。
+适用于高负载任务的最通用和功能最强大的表引擎。这些引擎的共同特点是可以快速插入数据并进行后续的后台数据处理。 MergeTree系列引擎支持数据复制（使用[复制\*](mergetree_family/replication.md) 的引擎版本），分区和一些其他引擎不支持的其他功能。
 
 该类型的引擎：
-\* [MergeTree](mergetree.md)
-\* [ReplacingMergeTree](replacingmergetree.md)
-\* [SummingMergeTree](summingmergetree.md)
-\* [AggregatingMergeTree](aggregatingmergetree.md)
-\* [CollapsingMergeTree](collapsingmergetree.md)
-\* [VersionedCollapsingMergeTree](versionedcollapsingmergetree.md)
-\* [GraphiteMergeTree](graphitemergetree.md)
+\* [MergeTree](mergetree_family/mergetree.md)
+\* [更换麦树](mergetree_family/replacingmergetree.md)
+\* [SummingMergeTree](mergetree_family/summingmergetree.md)
+\* [AggregatingMergeTree](mergetree_family/aggregatingmergetree.md)
+\* [折叠树](mergetree_family/collapsingmergetree.md)
+\* [版本集合在新树](mergetree_family/versionedcollapsingmergetree.md)
+\* [GraphiteMergeTree](mergetree_family/graphitemergetree.md)
 
-## Log {#log}
+## 日志 {#log}
 
-具有最小功能的[轻量级引擎](log_family.md)。当您需要快速写入许多小表（最多约100万行）并在以后整体读取它们时，该类型的引擎是最有效的。
+具有最小功能的[轻量级引擎](log_family/index.md)。当您需要快速写入许多小表（最多约100万行）并在以后整体读取它们时，该类型的引擎是最有效的。
 
 该类型的引擎：
 
--   \[TinyLog\](tinylog/）
--   \[StripeLog\](stripelog/）
--   [Log](#log)(log/）
+-   [TinyLog](log_family/tinylog.md)
+-   [StripeLog](log_family/stripelog.md)
+-   [日志](log_family/log.md)
 
-## Integration engines {#integration-engines}
+## 集成引擎 {#integration-engines}
 
 用于与其他的数据存储与处理系统集成的引擎。
 该类型的引擎：
 
--   [Kafka](kafka.md)
--   [MySQL](mysql.md)
--   [ODBC](odbc.md)
--   [JDBC](jdbc.md)
--   [HDFS](hdfs.md)
+-   [卡夫卡](integrations/kafka.md)
+-   [MySQL](integrations/mysql.md)
+-   [ODBC](integrations/odbc.md)
+-   [JDBC](integrations/jdbc.md)
+-   [HDFS](integrations/hdfs.md)
 
 ## 用于其他特定功能的引擎 {#yong-yu-qi-ta-te-ding-gong-neng-de-yin-qing}
 
 该类型的引擎：
 
--   [Distributed](distributed.md)
--   [MaterializedView](materializedview.md)
--   [Dictionary](dictionary.md)
--   [Merge](merge.md)
--   [File](file.md)
--   [Null](null.md)
--   [Set](set.md)
--   [Join](join.md)
--   [URL](url.md)
--   [View](view.md)
--   [Memory](memory.md)
--   [Buffer](buffer.md)
+-   [分布](special/distributed.md)
+-   [MaterializedView](special/materializedview.md)
+-   [字典](special/dictionary.md)
+-   [合并](special/merge.md)
+-   [文件](special/file.md)
+-   [Null](special/null.md)
+-   [设置](special/set.md)
+-   [加入我们](special/join.md)
+-   [URL](special/url.md)
+-   [查看](special/view.md)
+-   [记忆](special/memory.md)
+-   [缓冲区](special/buffer.md)
 
 # 虚拟列 {#xu-ni-lie}
 

docs/zh/engines/table_engines/integrations/hdfs.md

@@ -0,0 +1,123 @@
+---
+machine_translated: true
+machine_translated_rev: b111334d6614a02564cf32f379679e9ff970d9b1
+toc_priority: 36
+toc_title: HDFS
+---
+
+# HDFS {#table_engines-hdfs}
+
+该引擎提供了集成 [Apache Hadoop](https://en.wikipedia.org/wiki/Apache_Hadoop) 生态系统通过允许管理数据 [HDFS](https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/HdfsDesign.html)通过ClickHouse. 这个引擎是相似的
+到 [文件](../special/file.md) 和 [URL](../special/url.md) 引擎，但提供Hadoop特定的功能。
+
+## 用途 {#usage}
+
+``` sql
+ENGINE = HDFS(URI, format)
+```
+
+该 `URI` 参数是HDFS中的整个文件URI。
+该 `format` 参数指定一种可用的文件格式。 执行
+`SELECT` 查询时，格式必须支持输入，并执行
+`INSERT` queries – for output. The available formats are listed in the
+[格式](../../../interfaces/formats.md#formats) 科。
+路径部分 `URI` 可能包含水珠。 在这种情况下，表将是只读的。
+
+**示例:**
+
+**1.** 设置 `hdfs_engine_table` 表:
+
+``` sql
+CREATE TABLE hdfs_engine_table (name String, value UInt32) ENGINE=HDFS('hdfs://hdfs1:9000/other_storage', 'TSV')
+```
+
+**2.** 填充文件:
+
+``` sql
+INSERT INTO hdfs_engine_table VALUES ('one', 1), ('two', 2), ('three', 3)
+```
+
+**3.** 查询数据:
+
+``` sql
+SELECT * FROM hdfs_engine_table LIMIT 2
+```
+
+``` text
+┌─name─┬─value─┐
+│ one  │     1 │
+│ two  │     2 │
+└──────┴───────┘
+```
+
+## 实施细节 {#implementation-details}
+
+-   读取和写入可以并行
+-   不支持:
+    -   `ALTER` 和 `SELECT...SAMPLE` 操作。
+    -   索引。
+    -   复制。
+
+**路径中的水珠**
+
+多个路径组件可以具有globs。 对于正在处理的文件应该存在并匹配到整个路径模式。 文件列表确定在 `SELECT` （不在 `CREATE` 时刻）。
+
+-   `*` — Substitutes any number of any characters except `/` 包括空字符串。
+-   `?` — Substitutes any single character.
+-   `{some_string,another_string,yet_another_one}` — Substitutes any of strings `'some_string', 'another_string', 'yet_another_one'`.
+-   `{N..M}` — Substitutes any number in range from N to M including both borders.
+
+建筑与 `{}` 类似于 [远程](../../../sql_reference/table_functions/remote.md) 表功能。
+
+**示例**
+
+1.  假设我们在HDFS上有几个TSV格式的文件，其中包含以下Uri:
+
+-   ‘hdfs://hdfs1:9000/some\_dir/some\_file\_1’
+-   ‘hdfs://hdfs1:9000/some\_dir/some\_file\_2’
+-   ‘hdfs://hdfs1:9000/some\_dir/some\_file\_3’
+-   ‘hdfs://hdfs1:9000/another\_dir/some\_file\_1’
+-   ‘hdfs://hdfs1:9000/another\_dir/some\_file\_2’
+-   ‘hdfs://hdfs1:9000/another\_dir/some\_file\_3’
+
+1.  有几种方法可以创建由所有六个文件组成的表:
+
+<!-- -->
+
+``` sql
+CREATE TABLE table_with_range (name String, value UInt32) ENGINE = HDFS('hdfs://hdfs1:9000/{some,another}_dir/some_file_{1..3}', 'TSV')
+```
+
+另一种方式:
+
+``` sql
+CREATE TABLE table_with_question_mark (name String, value UInt32) ENGINE = HDFS('hdfs://hdfs1:9000/{some,another}_dir/some_file_?', 'TSV')
+```
+
+表由两个目录中的所有文件组成（所有文件都应满足query中描述的格式和模式):
+
+``` sql
+CREATE TABLE table_with_asterisk (name String, value UInt32) ENGINE = HDFS('hdfs://hdfs1:9000/{some,another}_dir/*', 'TSV')
+```
+
+!!! warning "警告"
+    如果文件列表包含带有前导零的数字范围，请单独使用带有大括号的构造或使用 `?`.
+
+**示例**
+
+创建具有名为文件的表 `file000`, `file001`, … , `file999`:
+
+``` sql
+CREARE TABLE big_table (name String, value UInt32) ENGINE = HDFS('hdfs://hdfs1:9000/big_dir/file{0..9}{0..9}{0..9}', 'CSV')
+```
+
+## 虚拟列 {#virtual-columns}
+
+-   `_path` — Path to the file.
+-   `_file` — Name of the file.
+
+**另请参阅**
+
+-   [虚拟列](../index.md#table_engines-virtual_columns)
+
+[原始文章](https://clickhouse.tech/docs/en/operations/table_engines/hdfs/) <!--hide-->

docs/zh/engines/table_engines/integrations/index.md

@@ -0,0 +1,8 @@
+---
+machine_translated: true
+machine_translated_rev: b111334d6614a02564cf32f379679e9ff970d9b1
+toc_folder_title: "\u96C6\u6210"
+toc_priority: 30
+---
+
+

docs/zh/engines/table_engines/integrations/jdbc.md

@@ -1,16 +1,19 @@
 ---
-en_copy: true
+machine_translated: true
+machine_translated_rev: b111334d6614a02564cf32f379679e9ff970d9b1
+toc_priority: 34
+toc_title: JDBC
 ---
 
 # JDBC {#table-engine-jdbc}
 
-Allows ClickHouse to connect to external databases via [JDBC](https://en.wikipedia.org/wiki/Java_Database_Connectivity).
+允许ClickHouse通过以下方式连接到外部数据库 [JDBC](https://en.wikipedia.org/wiki/Java_Database_Connectivity).
 
-To implement the JDBC connection, ClickHouse uses the separate program [clickhouse-jdbc-bridge](https://github.com/alex-krash/clickhouse-jdbc-bridge) that should run as a daemon.
+要实现JDBC连接，ClickHouse使用单独的程序 [ﾂ暗ｪﾂ氾环催ﾂ団ﾂ法ﾂ人](https://github.com/alex-krash/clickhouse-jdbc-bridge) 这应该作为守护进程运行。
 
-This engine supports the [Nullable](../../data_types/nullable.md) data type.
+该引擎支持 [可为空](../../../sql_reference/data_types/nullable.md) 数据类型。
 
-## Creating a Table {#creating-a-table}
+## 创建表 {#creating-a-table}
 
 ``` sql
 CREATE TABLE [IF NOT EXISTS] [db.]table_name
@@ -20,20 +23,20 @@ CREATE TABLE [IF NOT EXISTS] [db.]table_name
 ENGINE = JDBC(dbms_uri, external_database, external_table)
 ```
 
-**Engine Parameters**
+**发动机参数**
 
 -   `dbms_uri` — URI of an external DBMS.
 
-    Format: `jdbc:<driver_name>://<host_name>:<port>/?user=<username>&password=<password>`.
-    Example for MySQL: `jdbc:mysql://localhost:3306/?user=root&password=root`.
+    格式: `jdbc:<driver_name>://<host_name>:<port>/?user=<username>&password=<password>`.
+    Mysql的示例: `jdbc:mysql://localhost:3306/?user=root&password=root`.
 
 -   `external_database` — Database in an external DBMS.
 
 -   `external_table` — Name of the table in `external_database`.
 
-## Usage Example {#usage-example}
+## 用法示例 {#usage-example}
 
-Creating a table in MySQL server by connecting directly with it’s console client:
+通过直接与它的控制台客户端连接在MySQL服务器中创建一个表:
 
 ``` text
 mysql> CREATE TABLE `test`.`test` (
@@ -48,15 +51,15 @@ mysql> insert into test (`int_id`, `float`) VALUES (1,2);
 Query OK, 1 row affected (0,00 sec)
 
 mysql> select * from test;
-+--------+--------------+-------+----------------+
++------+----------+-----+----------+
 | int_id | int_nullable | float | float_nullable |
-+--------+--------------+-------+----------------+
++------+----------+-----+----------+
 |      1 |         NULL |     2 |           NULL |
-+--------+--------------+-------+----------------+
++------+----------+-----+----------+
 1 row in set (0,00 sec)
 ```
 
-Creating a table in ClickHouse server and selecting data from it:
+在ClickHouse服务器中创建表并从中选择数据:
 
 ``` sql
 CREATE TABLE jdbc_table
@@ -80,8 +83,8 @@ FROM jdbc_table
 └────────┴──────────────┴───────┴────────────────┘
 ```
 
-## See Also {#see-also}
+## 另请参阅 {#see-also}
 
--   [JDBC table function](../../query_language/table_functions/jdbc.md).
+-   [JDBC表函数](../../../sql_reference/table_functions/jdbc.md).
 
-[Original article](https://clickhouse.tech/docs/en/operations/table_engines/jdbc/) <!--hide-->
+[原始文章](https://clickhouse.tech/docs/en/operations/table_engines/jdbc/) <!--hide-->

docs/zh/engines/table_engines/integrations/kafka.md

@@ -1,4 +1,5 @@
-# Kafka {#kafka}
+
+# 卡夫卡 {#kafka}
 
 此引擎与 [Apache Kafka](http://kafka.apache.org/) 结合使用。
 
@@ -36,7 +37,7 @@ Kafka 特性：
 可选参数：
 
 -   `kafka_row_delimiter` - 每个消息体（记录）之间的分隔符。
--   `kafka_schema` – 如果解析格式需要一个 schema 时，此参数必填。例如，[Cap’n Proto](https://capnproto.org/) 需要 schema 文件路径以及根对象 `schema.capnp:Message` 的名字。
+-   `kafka_schema` – 如果解析格式需要一个 schema 时，此参数必填。例如，[普罗托船长](https://capnproto.org/) 需要 schema 文件路径以及根对象 `schema.capnp:Message` 的名字。
 -   `kafka_num_consumers` – 单个表的消费者数量。默认值是：`1`，如果一个消费者的吞吐量不足，则指定更多的消费者。消费者的总数不应该超过 topic 中分区的数量，因为每个分区只能分配一个消费者。
 
 示例：
@@ -103,7 +104,7 @@ Kafka 特性：
   SELECT level, sum(total) FROM daily GROUP BY level;
 ```
 
-为了提高性能，接受的消息被分组为 [max\_insert\_block\_size](../settings/settings.md#settings-max_insert_block_size) 大小的块。如果未在 [stream\_flush\_interval\_ms](../settings/settings.md) 毫秒内形成块，则不关心块的完整性，都会将数据刷新到表中。
+为了提高性能，接受的消息被分组为 [max\_insert\_block\_size](../../../operations/settings/settings.md#settings-max_insert_block_size) 大小的块。如果未在 [stream\_flush\_interval\_ms](../../../operations/settings/settings.md) 毫秒内形成块，则不关心块的完整性，都会将数据刷新到表中。
 
 停止接收主题数据或更改转换逻辑，请 detach 物化视图：
 
@@ -130,6 +131,6 @@ Kafka 特性：
   </kafka_logs>
 ```
 
-有关详细配置选项列表，请参阅 [librdkafka configuration reference](https://github.com/edenhill/librdkafka/blob/master/CONFIGURATION.md)。在 ClickHouse 配置中使用下划线 (`_`) ，并不是使用点 (`.`)。例如，`check.crcs=true` 将是 `<check_crcs>true</check_crcs>`。
+有关详细配置选项列表，请参阅 [librdkafka配置参考](https://github.com/edenhill/librdkafka/blob/master/CONFIGURATION.md)。在 ClickHouse 配置中使用下划线 (`_`) ，并不是使用点 (`.`)。例如，`check.crcs=true` 将是 `<check_crcs>true</check_crcs>`。
 
-[Original article](https://clickhouse.tech/docs/zh/operations/table_engines/kafka/) <!--hide-->
+[原始文章](https://clickhouse.tech/docs/zh/operations/table_engines/kafka/) <!--hide-->

docs/zh/engines/table_engines/integrations/mysql.md

@@ -1,3 +1,4 @@
+
 # MySQL {#mysql}
 
 MySQL 引擎可以对存储在远程 MySQL 服务器上的数据执行 `SELECT` 查询。
@@ -20,6 +21,6 @@ MySQL 引擎可以对存储在远程 MySQL 服务器上的数据执行 `SELECT`
 
 其余条件以及 `LIMIT` 采样约束语句仅在对MySQL的查询完成后才在ClickHouse中执行。
 
-`MySQL` 引擎不支持 [Nullable](../../data_types/nullable.md) 数据类型，因此，当从MySQL表中读取数据时，`NULL` 将转换为指定列类型的默认值（通常为0或空字符串）。
+`MySQL` 引擎不支持 [可为空](../../../engines/table_engines/integrations/mysql.md) 数据类型，因此，当从MySQL表中读取数据时，`NULL` 将转换为指定列类型的默认值（通常为0或空字符串）。
 
-[Original article](https://clickhouse.tech/docs/zh/operations/table_engines/mysql/) <!--hide-->
+[原始文章](https://clickhouse.tech/docs/zh/operations/table_engines/mysql/) <!--hide-->

docs/zh/engines/table_engines/integrations/odbc.md

@@ -0,0 +1,132 @@
+---
+machine_translated: true
+machine_translated_rev: b111334d6614a02564cf32f379679e9ff970d9b1
+toc_priority: 35
+toc_title: ODBC
+---
+
+# ODBC {#table-engine-odbc}
+
+允许ClickHouse通过以下方式连接到外部数据库 [ODBC](https://en.wikipedia.org/wiki/Open_Database_Connectivity).
+
+为了安全地实现ODBC连接，ClickHouse使用单独的程序 `clickhouse-odbc-bridge`. 如果直接从ODBC驱动程序加载 `clickhouse-server`，驱动程序问题可能会导致ClickHouse服务器崩溃。 ClickHouse自动启动 `clickhouse-odbc-bridge` 当它是必需的。 ODBC桥程序是从相同的软件包作为安装 `clickhouse-server`.
+
+该引擎支持 [可为空](../../../sql_reference/data_types/nullable.md) 数据类型。
+
+## 创建表 {#creating-a-table}
+
+``` sql
+CREATE TABLE [IF NOT EXISTS] [db.]table_name [ON CLUSTER cluster]
+(
+    name1 [type1],
+    name2 [type2],
+    ...
+)
+ENGINE = ODBC(connection_settings, external_database, external_table)
+```
+
+请参阅的详细说明 [CREATE TABLE](../../../sql_reference/statements/create.md#create-table-query) 查询。
+
+表结构可以与源表结构不同:
+
+-   列名应与源表中的列名相同，但您可以按任何顺序使用其中的一些列。
+-   列类型可能与源表中的列类型不同。 ClickHouse尝试 [投](../../../sql_reference/functions/type_conversion_functions.md#type_conversion_function-cast) ClickHouse数据类型的值。
+
+**发动机参数**
+
+-   `connection_settings` — Name of the section with connection settings in the `odbc.ini` 文件
+-   `external_database` — Name of a database in an external DBMS.
+-   `external_table` — Name of a table in the `external_database`.
+
+## 用法示例 {#usage-example}
+
+**通过ODBC从本地MySQL安装中检索数据**
+
+此示例检查Ubuntu Linux18.04和MySQL服务器5.7。
+
+确保安装了unixODBC和MySQL连接器。
+
+默认情况下（如果从软件包安装），ClickHouse以用户身份启动 `clickhouse`. 因此，您需要在MySQL服务器中创建和配置此用户。
+
+``` bash
+$ sudo mysql
+```
+
+``` sql
+mysql> CREATE USER 'clickhouse'@'localhost' IDENTIFIED BY 'clickhouse';
+mysql> GRANT ALL PRIVILEGES ON *.* TO 'clickhouse'@'clickhouse' WITH GRANT OPTION;
+```
+
+然后配置连接 `/etc/odbc.ini`.
+
+``` bash
+$ cat /etc/odbc.ini
+[mysqlconn]
+DRIVER = /usr/local/lib/libmyodbc5w.so
+SERVER = 127.0.0.1
+PORT = 3306
+DATABASE = test
+USERNAME = clickhouse
+PASSWORD = clickhouse
+```
+
+您可以使用 `isql` unixodbc安装中的实用程序。
+
+``` bash
+$ isql -v mysqlconn
++-------------------------+
+| Connected!                            |
+|                                       |
+...
+```
+
+MySQL中的表:
+
+``` text
+mysql> CREATE TABLE `test`.`test` (
+    ->   `int_id` INT NOT NULL AUTO_INCREMENT,
+    ->   `int_nullable` INT NULL DEFAULT NULL,
+    ->   `float` FLOAT NOT NULL,
+    ->   `float_nullable` FLOAT NULL DEFAULT NULL,
+    ->   PRIMARY KEY (`int_id`));
+Query OK, 0 rows affected (0,09 sec)
+
+mysql> insert into test (`int_id`, `float`) VALUES (1,2);
+Query OK, 1 row affected (0,00 sec)
+
+mysql> select * from test;
++------+----------+-----+----------+
+| int_id | int_nullable | float | float_nullable |
++------+----------+-----+----------+
+|      1 |         NULL |     2 |           NULL |
++------+----------+-----+----------+
+1 row in set (0,00 sec)
+```
+
+ClickHouse中的表，从MySQL表中检索数据:
+
+``` sql
+CREATE TABLE odbc_t
+(
+    `int_id` Int32,
+    `float_nullable` Nullable(Float32)
+)
+ENGINE = ODBC('DSN=mysqlconn', 'test', 'test')
+```
+
+``` sql
+SELECT * FROM odbc_t
+```
+
+``` text
+┌─int_id─┬─float_nullable─┐
+│      1 │           ᴺᵁᴸᴸ │
+└────────┴────────────────┘
+```
+
+## 另请参阅 {#see-also}
+
+-   [ODBC外部字典](../../../sql_reference/dictionaries/external_dictionaries/external_dicts_dict_sources.md#dicts-external_dicts_dict_sources-odbc)
+-   [ODBC表函数](../../../sql_reference/table_functions/odbc.md)
+
+[原始文章](https://clickhouse.tech/docs/en/operations/table_engines/odbc/) <!--hide-->

docs/zh/engines/table_engines/log_family/index.md

@@ -0,0 +1,8 @@
+---
+machine_translated: true
+machine_translated_rev: b111334d6614a02564cf32f379679e9ff970d9b1
+toc_folder_title: "\u65E5\u5FD7\u7CFB\u5217"
+toc_priority: 29
+---
+
+

docs/zh/engines/table_engines/log_family/log.md

@@ -1,5 +1,6 @@
-# Log {#log}
+
+# 日志 {#log}
 
 日志与 TinyLog 的不同之处在于，«标记» 的小文件与列文件存在一起。这些标记写在每个数据块上，并且包含偏移量，这些偏移量指示从哪里开始读取文件以便跳过指定的行数。这使得可以在多个线程中读取表数据。对于并发数据访问，可以同时执行读取操作，而写入操作则阻塞读取和其它写入。Log 引擎不支持索引。同样，如果写入表失败，则该表将被破坏，并且从该表读取将返回错误。Log 引擎适用于临时数据，write-once 表以及测试或演示目的。
 
-[Original article](https://clickhouse.tech/docs/zh/operations/table_engines/log/) <!--hide-->
+[原始文章](https://clickhouse.tech/docs/zh/operations/table_engines/log/) <!--hide-->

docs/zh/engines/table_engines/log_family/log_family.md

@@ -1,3 +1,4 @@
+
 # 日志引擎系列 {#table_engines-log-engine-family}
 
 这些引擎是为了需要写入许多小数据量（少于一百万行）的表的场景而开发的。
@@ -5,7 +6,7 @@
 这系列的引擎有：
 
 -   [StripeLog](stripelog.md)
--   [Log](log.md)
+-   [日志](log.md)
 -   [TinyLog](tinylog.md)
 
 ## 共同属性 {#table_engines-log-engine-family-common-properties}
@@ -16,7 +17,7 @@
 
 -   写入时将数据追加在文件末尾。
 
--   不支持[突变](../../query_language/alter.md#alter-mutations)操作。
+-   不支持[突变](../../../engines/table_engines/log_family/log_family.md#alter-mutations)操作。
 
 -   不支持索引。
 

docs/zh/engines/table_engines/log_family/stripelog.md

@@ -1,3 +1,4 @@
+
 # StripeLog {#table_engines-stripelog}
 
 该引擎属于日志引擎系列。请在[日志引擎系列](log_family.md)文章中查看引擎的共同属性和差异。
@@ -13,7 +14,7 @@
         ...
     ) ENGINE = StripeLog
 
-查看[建表](../../query_language/create.md#create-table-query)请求的详细说明。
+查看[建表](../../../engines/table_engines/log_family/stripelog.md#create-table-query)请求的详细说明。
 
 ## 写数据 {#table_engines-stripelog-writing-the-data}
 

docs/zh/engines/table_engines/log_family/tinylog.md

@@ -1,3 +1,4 @@
+
 # TinyLog {#tinylog}
 
 最简单的表引擎，用于将数据存储在磁盘上。每列都存储在单独的压缩文件中。写入时，数据将附加到文件末尾。
@@ -10,4 +11,4 @@
 
 在 Yandex.Metrica 中，TinyLog 表用于小批量处理的中间数据。
 
-[Original article](https://clickhouse.tech/docs/zh/operations/table_engines/tinylog/) <!--hide-->
+[原始文章](https://clickhouse.tech/docs/zh/operations/table_engines/tinylog/) <!--hide-->

docs/zh/engines/table_engines/mergetree_family/aggregatingmergetree.md

@@ -1,10 +1,11 @@
+
 # AggregatingMergeTree {#aggregatingmergetree}
 
 该引擎继承自 [MergeTree](mergetree.md)，并改变了数据片段的合并逻辑。 ClickHouse 会将相同主键的所有行（在一个数据片段内）替换为单个存储一系列聚合函数状态的行。
 
 可以使用 `AggregatingMergeTree` 表来做增量数据统计聚合，包括物化视图的数据聚合。
 
-引擎需使用 [AggregateFunction](../../data_types/nested_data_structures/aggregatefunction.md) 类型来处理所有列。
+引擎需使用 [AggregateFunction](../../../engines/table_engines/mergetree_family/aggregatingmergetree.md) 类型来处理所有列。
 
 如果要按一组规则来合并减少行数，则使用 `AggregatingMergeTree` 是合适的。
 
@@ -23,7 +24,7 @@ CREATE TABLE [IF NOT EXISTS] [db.]table_name [ON CLUSTER cluster]
 [SETTINGS name=value, ...]
 ```
 
-语句参数的说明，请参阅 [语句描述](../../query_language/create.md)。
+语句参数的说明，请参阅 [语句描述](../../../engines/table_engines/mergetree_family/aggregatingmergetree.md)。
 
 **子句**
 
@@ -50,7 +51,7 @@ CREATE TABLE [IF NOT EXISTS] [db.]table_name [ON CLUSTER cluster]
 
 ## SELECT 和 INSERT {#select-he-insert}
 
-插入数据，需使用带有聚合 -State- 函数的 [INSERT SELECT](../../query_language/insert_into.md) 语句。
+插入数据，需使用带有聚合 -State- 函数的 [INSERT SELECT](../../../engines/table_engines/mergetree_family/aggregatingmergetree.md) 语句。
 从 `AggregatingMergeTree` 表中查询数据时，需使用 `GROUP BY` 子句并且要使用与插入时相同的聚合函数，但后缀要改为 `-Merge` 。
 
 在 `SELECT` 查询的结果中，对于 ClickHouse 的所有输出格式 `AggregateFunction` 类型的值都实现了特定的二进制表示法。如果直接用 `SELECT` 导出这些数据，例如如用 `TabSeparated` 格式，那么这些导出数据也能直接用 `INSERT` 语句加载导入。