Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update tutorial.md [en→ru] #56125

Merged
merged 11 commits into from
Nov 1, 2023
Merged

Update tutorial.md [en→ru] #56125

merged 11 commits into from
Nov 1, 2023

Conversation

bezik
Copy link
Contributor

@bezik bezik commented Oct 30, 2023

Translation

Changelog category

  • Documentation

@alexey-milovidov alexey-milovidov added the can be tested Allows running workflows for external contributors label Oct 30, 2023
@robot-clickhouse-ci-2 robot-clickhouse-ci-2 added the pr-documentation Documentation PRs for the specific code PR label Oct 30, 2023
@robot-clickhouse-ci-2
Copy link
Contributor

robot-clickhouse-ci-2 commented Oct 30, 2023

This is an automated comment for commit 004593f with description of existing statuses. It's updated for the latest CI running

✅ Click here to open a full report in a separate page

Successful checks
Check nameDescriptionStatus
CI runningA meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR✅ success
Docs CheckBuilds and tests the documentation✅ success
Mergeable CheckChecks if all other necessary checks are successful✅ success
Push to DockerhubThe check for building and pushing the CI related docker images to docker hub✅ success
Style CheckRuns a set of checks to keep the code style clean. If some of tests failed, see the related log from the report✅ success

Copy link
Member

@vdimir vdimir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Спасибо за работу над документацией!

Предложил некоторые правки в комментариях.

docs/ru/getting-started/tutorial.md Outdated Show resolved Hide resolved
docs/ru/getting-started/tutorial.md Outdated Show resolved Hide resolved
docs/ru/getting-started/tutorial.md Outdated Show resolved Hide resolved
docs/ru/getting-started/tutorial.md Outdated Show resolved Hide resolved
docs/ru/getting-started/tutorial.md Outdated Show resolved Hide resolved
docs/ru/getting-started/tutorial.md Outdated Show resolved Hide resolved
docs/ru/getting-started/tutorial.md Outdated Show resolved Hide resolved
:::danger Notice
This approach is not suitable for the sharding of large tables. There’s a separate tool [clickhouse-copier](../operations/utilities/clickhouse-copier.md) that can re-shard arbitrary large tables.
:::danger Внимание!
Этот подход не годится для сегментирования больших таблиц. Есть инструмент [clickhouse-copier](../operations/utilities/clickhouse-copier.md), специально предназначенный для перераспределения любых больших таблиц.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Этот подход не годится для сегментирования больших таблиц. Есть инструмент [clickhouse-copier](../operations/utilities/clickhouse-copier.md), специально предназначенный для перераспределения любых больших таблиц.
Этот подход не подходит для сегментирования больших таблиц. Есть инструмент [clickhouse-copier](../operations/utilities/clickhouse-copier.md), специально предназначенный для перераспределения любых больших таблиц.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

«подход не походит…» — two words with the same root, probably, «подход не предназначен…», «подход нецелесообразен…»


To provide resilience in a production environment, we recommend that each shard should contain 2-3 replicas spread between multiple availability zones or datacenters (or at least racks). Note that ClickHouse supports an unlimited number of replicas.
В продуктивных окружениях для обеспечения надёжности мы рекомендуем чтобы каждый сегмент был защищён 2—3 репликами, разнесёнными на разные зоны отказоустойчивости или разные центры обработки данных (или хотя бы разные стойки). Особо отметим, что ClickHouse поддерживает неограниченное количество реплик.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
В продуктивных окружениях для обеспечения надёжности мы рекомендуем чтобы каждый сегмент был защищён 2—3 репликами, разнесёнными на разные зоны отказоустойчивости или разные центры обработки данных (или хотя бы разные стойки). Особо отметим, что ClickHouse поддерживает неограниченное количество реплик.
В производственных окружениях для обеспечения надёжности мы рекомендуем чтобы каждый сегмент был защищён 2—3 репликами, разнесёнными в разные зоны отказоустойчивости или разные центры обработки данных (или хотя бы разные стойки). Особо отметим, что ClickHouse поддерживает неограниченное количество реплик.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess ‘productive’ is more smoothly translated as calque “продуктивный”, because ‘промышленный’ in Russian means ‘industrial‘ (and not ‘productive’) in 99% of contexts.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[Sorry, I meant ‘производственный’ as the same of ’промышленный’, it‘s also means industrial-related in most of Russian contexts]

Copy link
Member

@vdimir vdimir Nov 1, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In original it's production environment and refers to environment used to serve business processes, isn't it? Not related to productive in a meaning able to produce large amounts of goods

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

‘Производственный‘ in Russian also tightly relates to [industrial] production, i. e. ability to produce large amounts of goods… ’В эксплуатационных окружениях…’?

docs/ru/getting-started/tutorial.md Outdated Show resolved Hide resolved
bezik and others added 10 commits October 31, 2023 15:05
Co-authored-by: vdimir <vdimir@clickhouse.com>
Co-authored-by: vdimir <vdimir@clickhouse.com>
Co-authored-by: vdimir <vdimir@clickhouse.com>
Co-authored-by: vdimir <vdimir@clickhouse.com>
Co-authored-by: vdimir <vdimir@clickhouse.com>
Co-authored-by: vdimir <vdimir@clickhouse.com>
Co-authored-by: vdimir <vdimir@clickhouse.com>
Co-authored-by: vdimir <vdimir@clickhouse.com>
Co-authored-by: vdimir <vdimir@clickhouse.com>
Co-authored-by: vdimir <vdimir@clickhouse.com>
@vdimir vdimir self-assigned this Oct 31, 2023
@vdimir vdimir merged commit b0f6b18 into ClickHouse:master Nov 1, 2023
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
can be tested Allows running workflows for external contributors pr-documentation Documentation PRs for the specific code PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants