Merge branch 'master' into force-documentation-3

This commit is contained in:
Alexey Milovidov 2022-08-27 19:31:44 +03:00 committed by GitHub
commit a6387ac0f7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
956 changed files with 1716 additions and 139 deletions

View File

@ -104,12 +104,16 @@ EOL
function stop()
{
local pid
# Preserve the pid, since the server can hung after the PID will be deleted.
pid="$(cat /var/run/clickhouse-server/clickhouse-server.pid)"
clickhouse stop --do-not-kill && return
# We failed to stop the server with SIGTERM. Maybe it hang, let's collect stacktraces.
kill -TERM "$(pidof gdb)" ||:
sleep 5
echo "thread apply all backtrace (on stop)" >> /test_output/gdb.log
gdb -batch -ex 'thread apply all backtrace' -p "$(cat /var/run/clickhouse-server/clickhouse-server.pid)" | ts '%Y-%m-%d %H:%M:%S' >> /test_output/gdb.log
gdb -batch -ex 'thread apply all backtrace' -p "$pid" | ts '%Y-%m-%d %H:%M:%S' >> /test_output/gdb.log
clickhouse stop --force
}
@ -441,6 +445,13 @@ else
[ -s /test_output/bc_check_fatal_messages.txt ] || rm /test_output/bc_check_fatal_messages.txt
fi
dmesg -T > /test_output/dmesg.log
# OOM in dmesg -- those are real
grep -q -F -e 'Out of memory: Killed process' -e 'oom_reaper: reaped process' -e 'oom-kill:constraint=CONSTRAINT_NONE' /test_output/dmesg.log \
&& echo -e 'OOM in dmesg\tFAIL' >> /test_output/test_results.tsv \
|| echo -e 'No OOM in dmesg\tOK' >> /test_output/test_results.tsv
tar -chf /test_output/coordination.tar /var/lib/clickhouse/coordination ||:
mv /var/log/clickhouse-server/stderr.log /test_output/
@ -462,5 +473,3 @@ for core in core.*; do
pigz $core
mv $core.gz /test_output/
done
dmesg -T > /test_output/dmesg.log

View File

@ -14,8 +14,6 @@ do
|| curl -fO "https://packages.clickhouse.com/tgz/stable/$PKG-$LATEST_VERSION.tgz"
done
exit 0
tar -xzvf "clickhouse-common-static-$LATEST_VERSION-${ARCH}.tgz" \
|| tar -xzvf "clickhouse-common-static-$LATEST_VERSION.tgz"
sudo "clickhouse-common-static-$LATEST_VERSION/install/doinst.sh"
@ -26,7 +24,7 @@ sudo "clickhouse-common-static-dbg-$LATEST_VERSION/install/doinst.sh"
tar -xzvf "clickhouse-server-$LATEST_VERSION-${ARCH}.tgz" \
|| tar -xzvf "clickhouse-server-$LATEST_VERSION.tgz"
sudo "clickhouse-server-$LATEST_VERSION/install/doinst.sh"
sudo "clickhouse-server-$LATEST_VERSION/install/doinst.sh" configure
sudo /etc/init.d/clickhouse-server start
tar -xzvf "clickhouse-client-$LATEST_VERSION-${ARCH}.tgz" \

View File

@ -54,7 +54,7 @@ the documentation is wrong. Go to the check report and look for `ERROR` and `WAR
Check that the description of your pull request conforms to the template
[PULL_REQUEST_TEMPLATE.md](https://github.com/ClickHouse/ClickHouse/blob/master/.github/PULL_REQUEST_TEMPLATE.md).
You have to specify a changelog category for your change (e.g., Bug Fix), and
write a user-readable message describing the change for [CHANGELOG.md](../whats-new/changelog/)
write a user-readable message describing the change for [CHANGELOG.md](../whats-new/changelog/index.md)
## Push To DockerHub

View File

@ -13,6 +13,8 @@ Syntax: `URL(URL [,Format] [,CompressionMethod])`
- 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 [Formats](../../../interfaces/formats.md#formats).
If this argument is not specified, ClickHouse detectes the format automatically from the suffix of the `URL` parameter. If the suffix of `URL` parameter does not match any supported formats, it fails to create table. For example, for engine expression `URL('http://localhost/test.json')`, `JSON` format is applied.
- `CompressionMethod` indicates that whether the HTTP body should be compressed. If the compression is enabled, the HTTP packets sent by the URL engine contain 'Content-Encoding' header to indicate which compression method is used.
To enable compression, please first make sure the remote HTTP endpoint indicated by the `URL` parameter supports corresponding compression algorithm.
@ -27,6 +29,11 @@ The supported `CompressionMethod` should be one of following:
- bz2
- snappy
- none
- auto
If `CompressionMethod` is not specified, it defaults to `auto`. This means ClickHouse detects compression method from the suffix of `URL` parameter automatically. If the suffix matches any of compression method listed above, corresponding compression is applied or there won't be any compression enabled.
For example, for engine expression `URL('http://localhost/test.gzip')`, `gzip` compression method is applied, but for `URL('http://localhost/test.fr')`, no compression is enabled because the suffix `fr` does not match any compression methods above.
## Usage {#using-the-engine-in-the-clickhouse-server}

View File

@ -140,8 +140,6 @@ do
|| curl -fO "https://packages.clickhouse.com/tgz/stable/$PKG-$LATEST_VERSION.tgz"
done
exit 0
tar -xzvf "clickhouse-common-static-$LATEST_VERSION-${ARCH}.tgz" \
|| tar -xzvf "clickhouse-common-static-$LATEST_VERSION.tgz"
sudo "clickhouse-common-static-$LATEST_VERSION/install/doinst.sh"
@ -152,7 +150,7 @@ sudo "clickhouse-common-static-dbg-$LATEST_VERSION/install/doinst.sh"
tar -xzvf "clickhouse-server-$LATEST_VERSION-${ARCH}.tgz" \
|| tar -xzvf "clickhouse-server-$LATEST_VERSION.tgz"
sudo "clickhouse-server-$LATEST_VERSION/install/doinst.sh"
sudo "clickhouse-server-$LATEST_VERSION/install/doinst.sh" configure
sudo /etc/init.d/clickhouse-server start
tar -xzvf "clickhouse-client-$LATEST_VERSION-${ARCH}.tgz" \

View File

@ -0,0 +1,8 @@
position: 80
label: 'About Us'
collapsible: true
collapsed: true
link:
type: generated-index
title: About Us
slug: /ru/about-us/

View File

@ -0,0 +1,8 @@
---
sidebar_label: Adopters
title: ClickHouse Adopters
---
import Adopters from '@site/docs/en/about-us/adopters.md';
<Adopters />

View File

@ -0,0 +1,8 @@
---
sidebar_label: Commercial Support
title: ClickHouse Commercial Support Service
---
import Support from '@site/docs/en/about-us/support.md';
<Support />

View File

@ -1,4 +1,5 @@
---
slug: /ru/commercial/cloud
sidebar_position: 1
sidebar_label: "Поставщики облачных услуг ClickHouse"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/commercial/
sidebar_position: 70
sidebar_label: "Коммерческие услуги"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/development/architecture
sidebar_position: 62
sidebar_label: "Обзор архитектуры ClickHouse"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/development/browse-code
sidebar_position: 72
sidebar_label: "Навигация по коду ClickHouse"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/development/build-osx
sidebar_position: 65
sidebar_label: Сборка на Mac OS X
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/development/contrib
sidebar_position: 71
sidebar_label: "Используемые сторонние библиотеки"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/development/developer-instruction
sidebar_position: 61
sidebar_label: "Инструкция для разработчиков"
---

View File

@ -1,3 +1,6 @@
---
slug: /ru/development/integrating_rust_libraries
---
# Интеграция библиотек на языке Rust в ClickHouse.
Интеграция библиотек будет описываться на основе работы проведенной для библиотеки BLAKE3.

View File

@ -1,4 +1,5 @@
---
slug: /ru/development/style
sidebar_position: 69
sidebar_label: "Как писать код на C++"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/database-engines/atomic
sidebar_position: 32
sidebar_label: Atomic
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/database-engines/
sidebar_position: 27
sidebar_label: "Движки баз данных"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/database-engines/lazy
sidebar_position: 31
sidebar_label: Lazy
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/database-engines/materialized-mysql
sidebar_position: 29
sidebar_label: "[experimental] MaterializedMySQL"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/database-engines/materialized-postgresql
sidebar_position: 30
sidebar_label: MaterializedPostgreSQL
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/database-engines/mysql
sidebar_position: 30
sidebar_label: MySQL
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/database-engines/postgresql
sidebar_position: 35
sidebar_label: PostgreSQL
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/database-engines/replicated
sidebar_position: 36
sidebar_label: Replicated
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/database-engines/sqlite
sidebar_position: 32
sidebar_label: SQLite
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/
sidebar_label: "Движки таблиц"
sidebar_position: 26
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/integrations/ExternalDistributed
sidebar_position: 12
sidebar_label: ExternalDistributed
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/integrations/embedded-rocksdb
sidebar_position: 9
sidebar_label: EmbeddedRocksDB
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/integrations/hdfs
sidebar_position: 6
sidebar_label: HDFS
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/integrations/
sidebar_label: "Движки таблиц для интеграции"
sidebar_position: 30
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/integrations/jdbc
sidebar_position: 3
sidebar_label: JDBC
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/integrations/kafka
sidebar_position: 8
sidebar_label: Kafka
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/integrations/materialized-postgresql
sidebar_position: 12
sidebar_label: MaterializedPostgreSQL
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/integrations/mongodb
sidebar_position: 5
sidebar_label: MongoDB
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/integrations/mysql
sidebar_position: 4
sidebar_label: MySQL
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/integrations/odbc
sidebar_position: 2
sidebar_label: ODBC
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/integrations/postgresql
sidebar_position: 11
sidebar_label: PostgreSQL
---

View File

@ -1,3 +1,6 @@
---
slug: /ru/engines/table-engines/integrations/rabbitmq
---
# RabbitMQ {#rabbitmq-engine}
Движок работает с [RabbitMQ](https://www.rabbitmq.com).

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/integrations/s3
sidebar_position: 4
sidebar_label: S3
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/integrations/sqlite
sidebar_position: 7
sidebar_label: SQLite
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/log-family/
sidebar_label: "Семейство Log"
sidebar_position: 29
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/log-family/log
sidebar_position: 33
sidebar_label: Log
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/log-family/stripelog
sidebar_position: 32
sidebar_label: StripeLog
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/log-family/tinylog
sidebar_position: 34
sidebar_label: TinyLog
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/mergetree-family/aggregatingmergetree
sidebar_position: 35
sidebar_label: AggregatingMergeTree
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/mergetree-family/collapsingmergetree
sidebar_position: 36
sidebar_label: CollapsingMergeTree
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/mergetree-family/custom-partitioning-key
sidebar_position: 32
sidebar_label: "Произвольный ключ партиционирования"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/mergetree-family/graphitemergetree
sidebar_position: 38
sidebar_label: GraphiteMergeTree
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/mergetree-family/
sidebar_label: MergeTree Family
sidebar_position: 28
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/mergetree-family/mergetree
sidebar_position: 30
sidebar_label: MergeTree
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/mergetree-family/replacingmergetree
sidebar_position: 33
sidebar_label: ReplacingMergeTree
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/mergetree-family/replication
sidebar_position: 31
sidebar_label: "Репликация данных"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/mergetree-family/summingmergetree
sidebar_position: 34
sidebar_label: SummingMergeTree
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/mergetree-family/versionedcollapsingmergetree
sidebar_position: 37
sidebar_label: VersionedCollapsingMergeTree
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/buffer
sidebar_position: 45
sidebar_label: Buffer
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/dictionary
sidebar_position: 35
sidebar_label: Dictionary
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/distributed
sidebar_position: 33
sidebar_label: Distributed
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/external-data
sidebar_position: 45
sidebar_label: "Внешние данные для обработки запроса"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/file
sidebar_position: 37
sidebar_label: File
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/
sidebar_label: "Специальные движки таблиц"
sidebar_position: 31
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/join
sidebar_position: 40
sidebar_label: Join
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/materializedview
sidebar_position: 43
sidebar_label: MaterializedView
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/memory
sidebar_position: 44
sidebar_label: Memory
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/merge
sidebar_position: 36
sidebar_label: Merge
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/null
sidebar_position: 38
sidebar_label: 'Null'
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/set
sidebar_position: 39
sidebar_label: Set
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/url
sidebar_position: 41
sidebar_label: URL
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/engines/table-engines/special/view
sidebar_position: 42
sidebar_label: View
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/general/columnar-database
title: Что такое столбцовая база данных?
sidebar_position: 101
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/general/dbms-naming
title: "Что означает название ClickHouse?"
sidebar_position: 10
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/general/how-do-i-contribute-code-to-clickhouse
title: How do I contribute code to ClickHouse?
sidebar_position: 120
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/general/
title: Общие вопросы о ClickHouse
toc_hidden_folder: true
sidebar_position: 1

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/general/mapreduce
title: Why not use something like MapReduce?
sidebar_position: 110
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/general/ne-tormozit
title: "What does “не тормозит” mean?"
sidebar_position: 11
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/general/olap
title: Что такое OLAP?
sidebar_position: 100
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/general/who-is-using-clickhouse
title: Кто пользуется ClickHouse?
sidebar_position: 9
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/general/why-clickhouse-is-so-fast
title: Почему ClickHouse так быстро работает?
sidebar_position: 8
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/
sidebar_label: F.A.Q.
sidebar_position: 76
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/integration/file-export
title: Как экспортировать данные из ClickHouse в файл?
sidebar_position: 10
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/integration/
title: Интеграция ClickHouse с другими системами
toc_hidden_folder: true
sidebar_position: 4

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/integration/json-import
title: Как импортировать JSON в ClickHouse?
sidebar_position: 11
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/integration/oracle-odbc
title: Что делать, если у меня проблема с кодировками при использовании Oracle через ODBC?
sidebar_position: 20
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/operations/delete-old-data
title: Возможно ли удалить старые записи из таблицы ClickHouse?
sidebar_position: 20
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/operations/
title: Вопросы о производительности серверов и кластеров ClickHouse
toc_hidden_folder: true
sidebar_position: 3

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/operations/multi-region-replication
title: Does ClickHouse support multi-region replication?
sidebar_position: 30
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/operations/production
title: Какую версию ClickHouse использовать?
sidebar_position: 10
---
@ -66,4 +67,4 @@ sidebar_position: 10
Часто компании, которые изначально ориентировались на релизы `lts`, позднее переходят на `stable`, поскольку хотят быстрее получать доступ к новым возможностям.
:::danger "Важно"
Мы всегда стремимся поддерживать совместимость релизов, но иногда это правило нарушается, и какие-то отдельные возможности в новых релизах становятся недоступны. Перед обновлением ClickHouse обязательно изучите [журнал изменений](../../whats-new/changelog/index.md), чтобы убедиться, что в нем нет объявлений о нарушении обратной совместимости.
Мы всегда стремимся поддерживать совместимость релизов, но иногда это правило нарушается, и какие-то отдельные возможности в новых релизах становятся недоступны. Перед обновлением ClickHouse обязательно изучите [журнал изменений](../../whats-new/changelog/index.mdx), чтобы убедиться, что в нем нет объявлений о нарушении обратной совместимости.

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/use-cases/
title: Вопросы о применении ClickHouse
toc_hidden_folder: true
sidebar_position: 2

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/use-cases/key-value
title: Можно ли использовать ClickHouse для хранения данных вида "ключ-значение"?
sidebar_position: 101
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/faq/use-cases/time-series
title: Можно ли использовать ClickHouse как базу данных временных рядов?
sidebar_position: 101
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/getting-started/example-datasets/amplab-benchmark
sidebar_position: 19
sidebar_label: AMPLab Big Data Benchmark
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/getting-started/example-datasets/brown-benchmark
sidebar_position: 20
sidebar_label: Brown University Benchmark
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/getting-started/example-datasets/cell-towers
sidebar_position: 21
sidebar_label: Вышки сотовой связи
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/getting-started/example-datasets/criteo
sidebar_position: 18
sidebar_label: "Терабайт логов кликов от Criteo"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/getting-started/example-datasets/
sidebar_label: "Тестовые массивы данных"
sidebar_position: 14
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/getting-started/example-datasets/menus
sidebar_position: 21
sidebar_label: Меню
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/getting-started/example-datasets/metrica
sidebar_position: 15
sidebar_label: "Анонимизированные данные Яндекс.Метрики"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/getting-started/example-datasets/nyc-taxi
sidebar_position: 20
sidebar_label: "Данные о такси в Нью-Йорке"
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/getting-started/example-datasets/ontime
sidebar_position: 21
sidebar_label: OnTime
---

View File

@ -1,4 +1,5 @@
---
slug: /ru/getting-started/example-datasets/opensky
sidebar_position: 20
sidebar_label: Набор данных о воздушном движении OpenSky Network 2020
---

Some files were not shown because too many files have changed in this diff Show More