ClickHouse/docs/en/table_engines/merge.rst

Merge
-----

The Merge engine (not to be confused with MergeTree) does not store data itself, but allows reading from any number of other tables simultaneously.
Reading is automatically parallelized. Writing to a table is not supported. When reading, the indexes of tables that are actually being read are used, if they exist.
The Merge engine accepts parameters: the database name and a regular expression for tables. Example:

.. code-block:: text

  Merge(hits, '^WatchLog')

- Data will be read from the tables in the 'hits' database with names that match the regex ``'^WatchLog'``.

Instead of the database name, you can use a constant expression that returns a string. For example, ``currentDatabase()``.

Regular expressions are re2 (similar to PCRE), case-sensitive. See the notes about escaping symbols in regular expressions in the "match" section.

When selecting tables to read, the Merge table itself will not be selected, even if it matches the regex. This is to avoid loops.
It is possible to create two Merge tables that will endlessly try to read each others' data. But don't do this.

The typical way to use the Merge engine is for working with a large number of TinyLog tables as if with a single table.

Virtual columns
~~~~~~~~~~~~~~~

Virtual columns are columns that are provided by the table engine, regardless of the table definition. In other words, these columns are not specified in CREATE TABLE, but they are accessible for SELECT.

Virtual columns differ from normal columns in the following ways:
 - They are not specified in table definitions.
 - Data can't be added to them with ``INSERT``.
 - When using ``INSERT`` without specifying the list of columns, virtual columns are ignored.
 - They are not selected when using the asterisk (``SELECT *``).
 - Virtual columns are not shown in ``SHOW CREATE TABLE`` and ``DESC TABLE`` queries.

A Merge table contains the virtual column **_table** of the String type. (If the table already has a '_table' column, the virtual column is named '_table1', and if it already has '_table1', it is named '_table2', and so on.) It contains the name of the table that data was read from.

If the WHERE or PREWHERE clause contains conditions for the '_table' column that do not depend on other table columns (as one of the conjunction elements, or as an entire expression), these conditions are used as an index. The conditions are performed on a data set of table names to read data from, and the read operation will be performed from only those tables that the condition was triggered on.