mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-09-29 21:20:49 +00:00
0a4a5b36cc
* Additional .gitignore entries * Merge a bunch of small articles about system tables into single one * Merge a bunch of small articles about formats into single one * Adapt table with formats to English docs too * Add SPb meetup link to main page * Move Utilities out of top level of docs (the location is probably not yet final) + translate couple articles * Merge MacOS.md into build_osx.md * Move Data types higher in ToC * Publish changelog on website alongside documentation * Few fixes for en/table_engines/file.md * Use smaller header sizes in changelogs * Group up table engines inside ToC * Move table engines out of top level too * Specificy in ToC that query language is SQL based. Thats a bit excessive, but catches eye. * Move stuff that is part of query language into respective folder * Move table functions lower in ToC * Lost redirects.txt update * Do not rely on comments in yaml + fix few ru titles * Extract major parts of queries.md into separate articles * queries.md has been supposed to be removed * Fix weird translation * Fix a bunch of links * There is only table of contents left * "Query language" is actually part of SQL abbreviation * Change filename in README.md too * fix mistype
20 lines
1.2 KiB
Markdown
20 lines
1.2 KiB
Markdown
# TinyLog
|
|
|
|
The simplest table engine, which stores data on a disk.
|
|
Each column is stored in a separate compressed file.
|
|
When writing, data is appended to the end of files.
|
|
|
|
Concurrent data access is not restricted in any way:
|
|
|
|
- If you are simultaneously reading from a table and writing to it in a different query, the read operation will complete with an error.
|
|
- If you are writing to a table in multiple queries simultaneously, the data will be broken.
|
|
|
|
The typical way to use this table is write-once: first just write the data one time, then read it as many times as needed.
|
|
Queries are executed in a single stream. In other words, this engine is intended for relatively small tables (recommended up to 1,000,000 rows).
|
|
It makes sense to use this table engine if you have many small tables, since it is simpler than the Log engine (fewer files need to be opened).
|
|
The situation when you have a large number of small tables guarantees poor productivity, but may already be used when working with another DBMS, and you may find it easier to switch to using TinyLog types of tables.
|
|
**Indexes are not supported.**
|
|
|
|
In Yandex.Metrica, TinyLog tables are used for intermediary data that is processed in small batches.
|
|
|