mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-10-06 16:40:48 +00:00
8623cb232c
* CLICKHOUSE-4063: less manual html @ index.md * CLICKHOUSE-4063: recommend markdown="1" in README.md * CLICKHOUSE-4003: manually purge custom.css for now * CLICKHOUSE-4064: expand <details> before any print (including to pdf) * CLICKHOUSE-3927: rearrange interfaces/formats.md a bit * CLICKHOUSE-3306: add few http headers * Remove copy-paste introduced in #3392 * Hopefully better chinese fonts #3392 * get rid of tabs @ custom.css * Apply comments and patch from #3384 * Add jdbc.md to ToC and some translation, though it still looks badly incomplete * minor punctuation * Add some backlinks to official website from mirrors that just blindly take markdown sources * Do not make fonts extra light * find . -name '*.md' -type f | xargs -I{} perl -pi -e 's//g' {} * find . -name '*.md' -type f | xargs -I{} perl -pi -e 's/ sql/g' {} * Remove outdated stuff from roadmap.md * Not so light font on front page too * Refactor Chinese formats.md to match recent changes in other languages
19 lines
690 B
Markdown
19 lines
690 B
Markdown
<a name="table_engines"></a>
|
|
|
|
# Table engines
|
|
|
|
The table engine (type of table) determines:
|
|
|
|
- How and where data is stored, where to write it to, and where to read it from.
|
|
- Which queries are supported, and how.
|
|
- Concurrent data access.
|
|
- Use of indexes, if present.
|
|
- Whether multithreaded request execution is possible.
|
|
- Data replication parameters.
|
|
|
|
When reading, the engine is only required to output the requested columns, but in some cases the engine can partially process data when responding to the request.
|
|
|
|
For most serious tasks, you should use engines from the `MergeTree` family.
|
|
|
|
[Original article](https://clickhouse.yandex/docs/en/operations/table_engines/) <!--hide-->
|