未验证 提交 e519e836 编写于 作者: E Eugene Klimov 提交者: GitHub

sync EN and RU version...

sync EN and RU version `operations/server-configuration-parameters/settings.md` add `text_log` description, translate to RU `trace_log.md` (#13923)

* fix docs link checks
recreate as new PR
https://github.com/ClickHouse/ClickHouse/pull/13190#issuecomment-676435412Signed-off-by: NSlach <bloodjazman@gmail.com>

* fix links after docs_check https://clickhouse-test-reports.s3.yandex.net/13923/0ce13be72e83665b7269c291f9efdf30c8533338/docs_check/docs_output.txtSigned-off-by: NSlach <bloodjazman@gmail.com>

* try to remove nowhere links in RU, EN, FA, ZN, FR, JA, TR version after https://clickhouse-test-reports.s3.yandex.net/13923/8a4bdfdc57b6b92cdae0651513d190e3f8ebcb23/docs_check/docs_output.txtSigned-off-by: NSlach <bloodjazman@gmail.com>

* fix link after https://clickhouse-test-reports.s3.yandex.net/13923/bc89725b138a8c8bdfa7f1e63698ec1957031cfe/docs_check/docs_output.txtSigned-off-by: NSlach <bloodjazman@gmail.com>
上级 dffd0a82
......@@ -339,13 +339,13 @@ Writing to the syslog is also supported. Config example:
</logger>
```
Keys:
Keys for syslog:
- use\_syslog — Required setting if you want to write to the syslog.
- address — The host\[:port\] of syslogd. If omitted, the local daemon is used.
- hostname — Optional. The name of the host that logs are sent from.
- facility — [The syslog facility keyword](https://en.wikipedia.org/wiki/Syslog#Facility) in uppercase letters with the “LOG\_” prefix: (`LOG_USER`, `LOG_DAEMON`, `LOG_LOCAL3`, and so on).
Default value: `LOG_USER` if `address` is specified, `LOG_DAEMON otherwise.`
Default value: `LOG_USER` if `address` is specified, `LOG_DAEMON` otherwise.
- format – Message format. Possible values: `bsd` and `syslog.`
## send\_crash\_reports {#server_configuration_parameters-logger}
......@@ -357,8 +357,8 @@ The server will need an access to public Internet via IPv4 (at the time of writi
Keys:
- `enabled` – Boolean flag to enable the feature. Set to `true` to allow sending crash reports.
- `endpoint`Overrides the Sentry endpoint.
- `enabled` – Boolean flag to enable the feature, `false` by default. Set to `true` to allow sending crash reports.
- `endpoint`You can override the Sentry endpoint URL for sending crash reports. It can be either separate Sentry account or your self-hosted Sentry instance. Use the [Sentry DSN](https://docs.sentry.io/error-reporting/quickstart/?platform=native#configure-the-sdk) syntax.
- `anonymize` - Avoid attaching the server hostname to crash report.
- `http_proxy` - Configure HTTP proxy for sending crash reports.
- `debug` - Sets the Sentry client into debug mode.
......@@ -397,6 +397,7 @@ The cache is shared for the server and memory is allocated as needed. The cache
``` xml
<mark_cache_size>5368709120</mark_cache_size>
```
## max\_server\_memory\_usage {#max_server_memory_usage}
Limits total RAM usage by the ClickHouse server.
......@@ -589,7 +590,8 @@ Use the following parameters to configure logging:
- `database` – Name of the database.
- `table` – Name of the system table.
- `partition_by` – Sets a [custom partitioning key](../../engines/table-engines/mergetree-family/custom-partitioning-key.md).
- `partition_by`[Custom partitioning key](../../engines/table-engines/mergetree-family/custom-partitioning-key.md) for a system table. Can't be used if `engine` defined.
- `engine` - [MergeTree Engine Definition](../../engines/table-engines/mergetree-family/mergetree.md#table_engine-mergetree-creating-a-table) for a system table. Can't be used if `partition_by` defined.
- `flush_interval_milliseconds` – Interval for flushing data from the buffer in memory to the table.
**Example**
......@@ -650,7 +652,8 @@ Use the following parameters to configure logging:
- `database` – Name of the database.
- `table` – Name of the system table the queries will be logged in.
- `partition_by` – Sets a [custom partitioning key](../../engines/table-engines/mergetree-family/custom-partitioning-key.md) for a table.
- `partition_by`[Custom partitioning key](../../engines/table-engines/mergetree-family/custom-partitioning-key.md) for a system table. Can't be used if `engine` defined.
- `engine` - [MergeTree Engine Definition](../../engines/table-engines/mergetree-family/mergetree.md#table_engine-mergetree-creating-a-table) for a system table. Can't be used if `partition_by` defined.
- `flush_interval_milliseconds` – Interval for flushing data from the buffer in memory to the table.
If the table doesn’t exist, ClickHouse will create it. If the structure of the query log changed when the ClickHouse server was updated, the table with the old structure is renamed, and a new table is created automatically.
......@@ -661,7 +664,7 @@ If the table doesn’t exist, ClickHouse will create it. If the structure of the
<query_log>
<database>system</database>
<table>query_log</table>
<partition_by>toMonday(event_date)</partition_by>
<engine>Engine = MergeTree PARTITION BY event_date ORDER BY event_time TTL event_date + INTERVAL 30 day</engine>
<flush_interval_milliseconds>7500</flush_interval_milliseconds>
</query_log>
```
......@@ -676,7 +679,8 @@ Use the following parameters to configure logging:
- `database` – Name of the database.
- `table` – Name of the system table the queries will be logged in.
- `partition_by` – Sets a [custom partitioning key](../../engines/table-engines/mergetree-family/custom-partitioning-key.md) for a system table.
- `partition_by`[Custom partitioning key](../../engines/table-engines/mergetree-family/custom-partitioning-key.md) for a system table. Can't be used if `engine` defined.
- `engine` - [MergeTree Engine Definition](../../engines/table-engines/mergetree-family/mergetree.md#table_engine-mergetree-creating-a-table) for a system table. Can't be used if `partition_by` defined.
- `flush_interval_milliseconds` – Interval for flushing data from the buffer in memory to the table.
If the table doesn’t exist, ClickHouse will create it. If the structure of the query thread log changed when the ClickHouse server was updated, the table with the old structure is renamed, and a new table is created automatically.
......@@ -692,6 +696,34 @@ If the table doesn’t exist, ClickHouse will create it. If the structure of the
</query_thread_log>
```
## text\_log {#server_configuration_parameters-text_log}
Settings for the [text\_log](../../operations/system-tables/text_log.md#system_tables-text_log) system table for logging text messages.
Parameters:
- `level` — Maximum Message Level (by default `Trace`) which will be stored in a table.
- `database` — Database name.
- `table` — Table name.
- `partition_by`[Custom partitioning key](../../engines/table-engines/mergetree-family/custom-partitioning-key.md) for a system table. Can't be used if `engine` defined.
- `engine` - [MergeTree Engine Definition](../../engines/table-engines/mergetree-family/mergetree.md#table_engine-mergetree-creating-a-table) for a system table. Can't be used if `partition_by` defined.
- `flush_interval_milliseconds` — Interval for flushing data from the buffer in memory to the table.
**Example**
```xml
<yandex>
<text_log>
<level>notice</level>
<database>system</database>
<table>text_log</table>
<flush_interval_milliseconds>7500</flush_interval_milliseconds>
<!-- <partition_by>event_date</partition_by> -->
<engine>Engine = MergeTree PARTITION BY event_date ORDER BY event_time TTL event_date + INTERVAL 30 day</engine>
</text_log>
</yandex>
```
## trace\_log {#server_configuration_parameters-trace_log}
Settings for the [trace\_log](../../operations/system-tables/trace_log.md#system_tables-trace_log) system table operation.
......@@ -700,7 +732,8 @@ Parameters:
- `database` — Database for storing a table.
- `table` — Table name.
- `partition_by`[Custom partitioning key](../../engines/table-engines/mergetree-family/custom-partitioning-key.md) for a system table.
- `partition_by`[Custom partitioning key](../../engines/table-engines/mergetree-family/custom-partitioning-key.md) for a system table. Can't be used if `engine` defined.
- `engine` - [MergeTree Engine Definition](../../engines/table-engines/mergetree-family/index.md) for a system table. Can't be used if `partition_by` defined.
- `flush_interval_milliseconds` — Interval for flushing data from the buffer in memory to the table.
The default server configuration file `config.xml` contains the following settings section:
......@@ -717,7 +750,7 @@ The default server configuration file `config.xml` contains the following settin
## query\_masking\_rules {#query-masking-rules}
Regexp-based rules, which will be applied to queries as well as all log messages before storing them in server logs,
`system.query_log`, `system.text_log`, `system.processes` table, and in logs sent to the client. That allows preventing
`system.query_log`, `system.text_log`, `system.processes` tables, and in logs sent to the client. That allows preventing
sensitive data leakage from SQL queries (like names, emails, personal
identifiers or credit card numbers) to logs.
......
# system.text_log {#system-tables-text-log}
# system.text\_log {#system_tables-text_log}
Contains logging entries. Logging level which goes to this table can be limited with `text_log.level` server setting.
......
......@@ -532,7 +532,7 @@ Columna:
- `query` (String) – The query text. For `INSERT`, no incluye los datos para insertar.
- `query_id` (String) – Query ID, if defined.
## sistema.text\_log {#system-tables-text-log}
## sistema.text\_log {#system_tables-text_log}
Contiene entradas de registro. El nivel de registro que va a esta tabla se puede limitar con `text_log.level` configuración del servidor.
......
......@@ -532,7 +532,7 @@ CurrentMetric_ReplicatedChecks: 0
- `query` (String) – The query text. For `INSERT` این شامل داده ها برای وارد کردن نیست.
- `query_id` (String) – Query ID, if defined.
## سیستم.\_خروج {#system-tables-text-log}
## سیستم.\_خروج {#system_tables-text_log}
شامل ورودی ورود به سیستم. سطح ورود به سیستم که می رود به این جدول را می توان با محدود `text_log.level` تنظیم سرور.
......
......@@ -532,7 +532,7 @@ Colonne:
- `query` (String) – The query text. For `INSERT` il n'inclut pas les données à insérer.
- `query_id` (String) – Query ID, if defined.
## système.text\_log {#system-tables-text-log}
## système.text\_log {#system_tables-text_log}
Contient des entrées de journalisation. Niveau de journalisation qui va à cette table peut être limité `text_log.level` paramètre de serveur.
......
......@@ -320,10 +320,9 @@ ou
LAYOUT(DIRECT())
```
### complex\_key\_cache {#complex-key-cache}
Ce type de stockage est pour une utilisation avec composite [touches](external-dicts-dict-structure.md). Semblable à `direct`.
### complex\_key\_direct {#complex-key-direct}
Ce type de stockage est destiné à être utilisé avec des [clés](../../../sql-reference/dictionaries/external-dictionaries/external-dicts-dict-structure.md) composites. Similaire à `direct`
### ip\_trie {#ip-trie}
......
......@@ -532,7 +532,7 @@ CurrentMetric_ReplicatedChecks: 0
- `query` (String) – The query text. For `INSERT`,挿入するデータは含まれません。
- `query_id` (String) – Query ID, if defined.
## システムtext\_log {#system-tables-text-log}
## システムtext\_log {#system_tables-text_log}
を含むログイン作品の応募がありました。 ログレベルがこのテーブルで限定 `text_log.level` サーバー設定。
......
# system.text_log {#system-tables-text-log}
# system.text_log {#system_tables-text_log}
Содержит записи логов. Уровень логирования для таблицы может быть ограничен параметром сервера `text_log.level`.
......
# system.trace_log {#system_tables-trace_log}
Contains stack traces collected by the sampling query profiler.
Содержит экземпляры трассировки стека адресов вызова, собранные с помощью семплирующего профайлера запросов.
ClickHouse creates this table when the [trace\_log](../server-configuration-parameters/settings.md#server_configuration_parameters-trace_log) server configuration section is set. Also the [query_profiler_real_time_period_ns](../settings/settings.md#query_profiler_real_time_period_ns) and [query_profiler_cpu_time_period_ns](../settings/settings.md#query_profiler_cpu_time_period_ns) settings should be set.
ClickHouse создает эту таблицу когда утсановлена настройка [trace\_log](../server-configuration-parameters/settings.md#server_configuration_parameters-trace_log) в конфигурационном файле сервереа. А также настройки [query_profiler_real_time_period_ns](../settings/settings.md#query_profiler_real_time_period_ns) и [query_profiler_cpu_time_period_ns](../settings/settings.md#query_profiler_cpu_time_period_ns).
To analyze logs, use the `addressToLine`, `addressToSymbol` and `demangle` introspection functions.
Для анализа stack traces, используйте функции интроспекции `addressToLine`, `addressToSymbol` и `demangle`.
Columns:
Колонки:
- `event_date`([Date](../../sql-reference/data-types/date.md)) — Date of sampling moment.
- `event_date`([Date](../../sql-reference/data-types/date.md)) — Дата в момент снятия экземпляра стэка адресов вызова.
- `event_time`([DateTime](../../sql-reference/data-types/datetime.md)) — Timestamp of sampling moment.
- `event_time`([DateTime](../../sql-reference/data-types/datetime.md)) — Дата и время в момент снятия экземпляра стэка адресов вызова.
- `revision`([UInt32](../../sql-reference/data-types/int-uint.md)) — ClickHouse server build revision.
- `revision`([UInt32](../../sql-reference/data-types/int-uint.md)) — ревизия сборки сервера ClickHouse.
When connecting to server by `clickhouse-client`, you see the string similar to `Connected to ClickHouse server version 19.18.1 revision 54429.`. This field contains the `revision`, but not the `version` of a server.
Во время соединения с сервером через `clickhouse-client`, вы видите строку похожую на `Connected to ClickHouse server version 19.18.1 revision 54429.`. Это поле содержит номер после `revision`, но не содержит строку после `version`.
- `timer_type`([Enum8](../../sql-reference/data-types/enum.md)) — Timer type:
- `timer_type`([Enum8](../../sql-reference/data-types/enum.md)) — Тип таймера:
- `Real` represents wall-clock time.
- `CPU` represents CPU time.
- `Real` означает wall-clock время.
- `CPU` означает относительное CPU время.
- `thread_number`([UInt32](../../sql-reference/data-types/int-uint.md)) — Thread identifier.
- `thread_number`([UInt32](../../sql-reference/data-types/int-uint.md)) — Идентификатор треда.
- `query_id`([String](../../sql-reference/data-types/string.md)) — Query identifier that can be used to get details about a query that was running from the [query_log](#system_tables-query_log) system table.
- `query_id`([String](../../sql-reference/data-types/string.md)) — Идентификатор запроса который может быть использован для получения деталей о запросе из таблицы [query_log](query_log.md#system_tables-query_log) system table.
- `trace`([Array(UInt64)](../../sql-reference/data-types/array.md)) — Stack trace at the moment of sampling. Each element is a virtual memory address inside ClickHouse server process.
- `trace`([Array(UInt64)](../../sql-reference/data-types/array.md)) — Трассировка стека адресов вызова в момент семплирования. Каждый элемент массива это адрес виртуальной памяти внутри процесса сервера ClickHouse.
**Example**
**Пример**
``` sql
SELECT * FROM system.trace_log LIMIT 1 \G
......
......@@ -532,7 +532,7 @@ Sütun:
- `query` (String) – The query text. For `INSERT`, eklemek için veri içermez.
- `query_id` (String) – Query ID, if defined.
## sistem.text\_log {#system-tables-text-log}
## sistem.text\_log {#system_tables-text_log}
Günlük girişleri içerir. Bu tabloya giden günlük seviyesi ile sınırlı olabilir `text_log.level` sunucu ayarı.
......
......@@ -1252,3 +1252,61 @@ ClickHouse生成异常
默认值:16。
[原始文章](https://clickhouse.tech/docs/en/operations/settings/settings/) <!-- hide -->
## transform\_null\_in {#transform_null_in}
[IN](../../sql-reference/operators/in.md) 运算符启用[NULL](../../sql-reference/syntax.md#null-literal) 值的相等性。
默认情况下,无法比较 `NULL` 值,因为 `NULL` 表示未定义的值。 因此,比较 `expr = NULL` 必须始终返回 `false`。 在此设置下,`NULL = NULL` 为IN运算符返回 `true`.
可能的值:
- 0 — 比较 `IN` 运算符中 `NULL` 值将返回 `false`
- 1 — 比较 `IN` 运算符中 `NULL` 值将返回 `true`
默认值:0。
**例**
考虑`null_in`表:
``` text
┌──idx─┬─────i─┐
│ 1 │ 1 │
│ 2 │ NULL │
│ 3 │ 3 │
└──────┴───────┘
```
查询:
``` sql
SELECT idx, i FROM null_in WHERE i IN (1, NULL) SETTINGS transform_null_in = 0;
```
结果:
``` text
┌──idx─┬────i─┐
│ 1 │ 1 │
└──────┴──────┘
```
查询:
``` sql
SELECT idx, i FROM null_in WHERE i IN (1, NULL) SETTINGS transform_null_in = 1;
```
结果:
``` text
┌──idx─┬─────i─┐
│ 1 │ 1 │
│ 2 │ NULL │
└──────┴───────┘
```
**另请参阅**
- [IN 运算符中的 NULL 处理](../../sql-reference/operators/in.md#in-null-processing)
......@@ -3,7 +3,7 @@ machine_translated: true
machine_translated_rev: 5decc73b5dc60054f19087d3690c4eb99446a6c3
---
# 系统。text\_log {#system-tables-text-log}
# 系统。text\_log {#system_tables-text_log}
包含日志记录条目。 进入该表的日志记录级别可以通过以下方式进行限制 `text_log.level` 服务器设置。
......
......@@ -89,15 +89,12 @@ CH只支持用单引号包含的字母。特殊字符可通过反斜杠进行转
在字符串中,你至少需要对 `'``\` 进行转义。单引号可以使用单引号转义,例如 `'It\'s'` 和 `'It''s'` 是相同的。
### 括号 {#compound}
数组都是使用方括号进行构造 `[1, 2, 3]`,元组则使用圆括号 `(1, 'Hello, world!', 2)`
数组都是使用方括号进行构造 `[1, 2, 3]`,元组则使用圆括号 `(1, 'Hello, world!', 2)`
从技术上来讲,这些都不是字符串,而是包含创建数组和元组运算符的表达式。
创建一个数组必须至少包含一个元素,创建一个元组至少包含2个元素
当元组出现在 `SELECT` 查询的 `IN` 部分时,是一种例外情形。查询结果可以包含元组,但是元组类型不能保存到数据库中(除非表采用 [内存表](../engines/table-engines/special/memory.md)引擎)
### NULL值 {#null-literal}
代表不存在的值
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册