ClickHouse/docs/en/engines/table-engines/index.md

slug	toc_folder_title	toc_priority	toc_title
/en/engines/table-engines/	Table Engines	26	Introduction

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 multithread request execution is possible.
• Data replication parameters.

Engine Families

MergeTree

The most universal and functional table engines for high-load tasks. The property shared by these engines is quick data insertion with subsequent background data processing. MergeTree family engines support data replication (with Replicated* versions of engines), partitioning, secondary data-skipping indexes, and other features not supported in other engines.

Engines in the family:

• MergeTree
• ReplacingMergeTree
• SummingMergeTree
• AggregatingMergeTree
• CollapsingMergeTree
• VersionedCollapsingMergeTree
• GraphiteMergeTree

Log

Lightweight engines with minimum functionality. They’re the most effective when you need to quickly write many small tables (up to approximately 1 million rows) and read them later as a whole.

Engines in the family:

• TinyLog
• StripeLog
• Log

Integration Engines

Engines for communicating with other data storage and processing systems.

Engines in the family:

• ODBC
• JDBC
• MySQL
• MongoDB
• Redis
• HDFS
• S3
• Kafka
• EmbeddedRocksDB
• RabbitMQ
• PostgreSQL
• S3Queue

Special Engines

Engines in the family:

• Distributed
• MaterializedView
• Dictionary
• Merge
• File
• Null
• Set
• Join
• URL
• View
• Memory
• Buffer
• KeeperMap

Virtual Columns

Virtual column is an integral table engine attribute that is defined in the engine source code.

You shouldn’t specify virtual columns in the CREATE TABLE query and you can’t see them in SHOW CREATE TABLE and DESCRIBE TABLE query results. Virtual columns are also read-only, so you can’t insert data into virtual columns.

To select data from a virtual column, you must specify its name in the SELECT query. SELECT * does not return values from virtual columns.

If you create a table with a column that has the same name as one of the table virtual columns, the virtual column becomes inaccessible. We do not recommend doing this. To help avoid conflicts, virtual column names are usually prefixed with an underscore.