2020-04-03 13:23:32 +00:00
---
2022-08-28 14:53:34 +00:00
slug: /en/engines/table-engines/integrations/mysql
2023-06-23 13:16:22 +00:00
sidebar_position: 138
2022-04-09 13:29:05 +00:00
sidebar_label: MySQL
2020-04-03 13:23:32 +00:00
---
2024-03-15 01:56:28 +00:00
import CloudAvailableBadge from '@theme/badges/CloudAvailableBadge';
2024-03-15 01:30:18 +00:00
2024-03-15 01:56:28 +00:00
# MySQL Table Engine
2018-04-23 06:20:21 +00:00
2024-03-15 01:56:28 +00:00
< CloudAvailableBadge / >
2024-03-15 01:30:18 +00:00
2021-06-03 17:12:19 +00:00
The MySQL engine allows you to perform `SELECT` and `INSERT` queries on data that is stored on a remote MySQL server.
2018-04-23 06:20:21 +00:00
2020-03-20 10:10:48 +00:00
## Creating a Table {#creating-a-table}
2018-04-23 06:20:21 +00:00
2020-03-20 10:10:48 +00:00
``` sql
2019-05-18 17:25:58 +00:00
CREATE TABLE [IF NOT EXISTS] [db.]table_name [ON CLUSTER cluster]
(
name1 [type1] [DEFAULT|MATERIALIZED|ALIAS expr1] [TTL expr1],
name2 [type2] [DEFAULT|MATERIALIZED|ALIAS expr2] [TTL expr2],
...
2023-12-06 22:58:47 +00:00
) ENGINE = MySQL({host:port, database, table, user, password[, replace_query, on_duplicate_clause] | named_collection[, option=value [,..]]})
2021-05-15 04:40:43 +00:00
SETTINGS
2022-06-29 19:52:32 +00:00
[ connection_pool_size=16, ]
[ connection_max_tries=3, ]
[ connection_wait_timeout=5, ]
[ connection_auto_close=true, ]
[ connect_timeout=10, ]
[ read_write_timeout=300 ]
2021-05-15 04:40:43 +00:00
;
2018-09-04 11:18:59 +00:00
```
2018-04-23 06:20:21 +00:00
2020-07-09 15:10:35 +00:00
See a detailed description of the [CREATE TABLE ](../../../sql-reference/statements/create/table.md#create-table-query ) query.
2019-05-18 17:25:58 +00:00
2019-05-30 15:12:56 +00:00
The table structure can differ from the original MySQL table structure:
2019-05-18 17:25:58 +00:00
2023-04-19 15:55:29 +00:00
- Column names should be the same as in the original MySQL table, but you can use just some of these columns and in any order.
- Column types may differ from those in the original MySQL table. ClickHouse tries to [cast ](../../../engines/database-engines/mysql.md#data_types-support ) values to the ClickHouse data types.
- The [external_table_functions_use_nulls ](../../../operations/settings/settings.md#external-table-functions-use-nulls ) setting defines how to handle Nullable columns. Default value: 1. If 0, the table function does not make Nullable columns and inserts default values instead of nulls. This is also applicable for NULL values inside arrays.
2019-05-18 17:25:58 +00:00
2023-06-19 10:34:36 +00:00
:::note
The MySQL Table Engine is currently not available on the ClickHouse builds for MacOS ([issue](https://github.com/ClickHouse/ClickHouse/issues/21191))
:::
2019-05-18 17:25:58 +00:00
**Engine Parameters**
2018-09-04 11:18:59 +00:00
2023-04-19 15:55:29 +00:00
- `host:port` — MySQL server address.
- `database` — Remote database name.
- `table` — Remote table name.
- `user` — MySQL user.
- `password` — User password.
- `replace_query` — Flag that converts `INSERT INTO` queries to `REPLACE INTO` . If `replace_query=1` , the query is substituted.
- `on_duplicate_clause` — The `ON DUPLICATE KEY on_duplicate_clause` expression that is added to the `INSERT` query.
2020-03-21 04:11:51 +00:00
Example: `INSERT INTO t (c1,c2) VALUES ('a', 2) ON DUPLICATE KEY UPDATE c2 = c2 + 1` , where `on_duplicate_clause` is `UPDATE c2 = c2 + 1` . See the [MySQL documentation ](https://dev.mysql.com/doc/refman/8.0/en/insert-on-duplicate.html ) to find which `on_duplicate_clause` you can use with the `ON DUPLICATE KEY` clause.
To specify `on_duplicate_clause` you need to pass `0` to the `replace_query` parameter. If you simultaneously pass `replace_query = 1` and `on_duplicate_clause` , ClickHouse generates an exception.
2018-10-22 18:45:23 +00:00
2023-12-06 22:58:47 +00:00
Arguments also can be passed using [named collections ](/docs/en/operations/named-collections.md ). In this case `host` and `port` should be specified separately. This approach is recommended for production environment.
2020-03-20 10:10:48 +00:00
Simple `WHERE` clauses such as `=, !=, >, >=, <, <=` are executed on the MySQL server.
2018-09-04 11:18:59 +00:00
The rest of the conditions and the `LIMIT` sampling constraint are executed in ClickHouse only after the query to MySQL finishes.
2018-04-23 06:20:21 +00:00
2021-06-27 09:25:52 +00:00
Supports multiple replicas that must be listed by `|` . For example:
2021-06-24 19:29:57 +00:00
```sql
CREATE TABLE test_replicas (id UInt32, name String, age UInt32, money UInt32) ENGINE = MySQL(`mysql{2|3|4}:3306`, 'clickhouse', 'test_replicas', 'root', 'clickhouse');
```
2020-03-20 10:10:48 +00:00
## Usage Example {#usage-example}
2019-05-18 17:25:58 +00:00
2023-12-06 22:58:47 +00:00
Create table in MySQL:
2019-05-18 17:25:58 +00:00
2020-03-20 10:10:48 +00:00
``` text
2019-05-18 17:25:58 +00:00
mysql> CREATE TABLE `test` .`test` (
-> `int_id` INT NOT NULL AUTO_INCREMENT,
-> `int_nullable` INT NULL DEFAULT NULL,
-> `float` FLOAT NOT NULL,
-> `float_nullable` FLOAT NULL DEFAULT NULL,
-> PRIMARY KEY (`int_id`));
Query OK, 0 rows affected (0,09 sec)
mysql> insert into test (`int_id`, `float` ) VALUES (1,2);
Query OK, 1 row affected (0,00 sec)
mysql> select * from test;
2020-04-03 13:23:32 +00:00
+------+----------+-----+----------+
2019-05-18 17:25:58 +00:00
| int_id | int_nullable | float | float_nullable |
2020-04-03 13:23:32 +00:00
+------+----------+-----+----------+
2019-05-18 17:25:58 +00:00
| 1 | NULL | 2 | NULL |
2020-04-03 13:23:32 +00:00
+------+----------+-----+----------+
2019-05-18 17:25:58 +00:00
1 row in set (0,00 sec)
```
2023-12-06 22:58:47 +00:00
Create table in ClickHouse using plain arguments:
2019-05-18 17:25:58 +00:00
2020-03-20 10:10:48 +00:00
``` sql
2019-05-18 17:25:58 +00:00
CREATE TABLE mysql_table
(
`float_nullable` Nullable(Float32),
`int_id` Int32
)
ENGINE = MySQL('localhost:3306', 'test', 'test', 'bayonet', '123')
```
2020-03-20 10:10:48 +00:00
2023-12-06 22:58:47 +00:00
Or using [named collections ](/docs/en/operations/named-collections.md ):
```sql
CREATE NAMED COLLECTION creds AS
host = 'localhost',
port = 3306,
database = 'test',
user = 'bayonet',
password = '123';
CREATE TABLE mysql_table
(
`float_nullable` Nullable(Float32),
`int_id` Int32
)
ENGINE = MySQL(creds, table='test')
```
Retrieving data from MySQL table:
2020-03-20 10:10:48 +00:00
``` sql
2019-09-24 23:07:52 +00:00
SELECT * FROM mysql_table
2019-05-18 17:25:58 +00:00
```
2020-03-20 10:10:48 +00:00
``` text
2019-05-18 17:25:58 +00:00
┌─float_nullable─┬─int_id─┐
│ ᴺᵁᴸᴸ │ 1 │
└────────────────┴────────┘
```
2021-11-25 16:59:14 +00:00
## Settings {#mysql-settings}
Default settings are not very efficient, since they do not even reuse connections. These settings allow you to increase the number of queries run by the server per second.
### connection_auto_close {#connection-auto-close}
Allows to automatically close the connection after query execution, i.e. disable connection reuse.
Possible values:
2023-04-19 15:55:29 +00:00
- 1 — Auto-close connection is allowed, so the connection reuse is disabled
- 0 — Auto-close connection is not allowed, so the connection reuse is enabled
2021-11-25 16:59:14 +00:00
Default value: `1` .
### connection_max_tries {#connection-max-tries}
Sets the number of retries for pool with failover.
Possible values:
2023-04-19 15:55:29 +00:00
- Positive integer.
- 0 — There are no retries for pool with failover.
2021-11-25 16:59:14 +00:00
Default value: `3` .
### connection_pool_size {#connection-pool-size}
Size of connection pool (if all connections are in use, the query will wait until some connection will be freed).
Possible values:
2023-04-19 15:55:29 +00:00
- Positive integer.
2021-11-25 16:59:14 +00:00
Default value: `16` .
2022-06-29 19:52:32 +00:00
### connection_wait_timeout {#connection-wait-timeout}
Timeout (in seconds) for waiting for free connection (in case of there is already connection_pool_size active connections), 0 - do not wait.
Possible values:
2023-04-19 15:55:29 +00:00
- Positive integer.
2022-06-29 19:52:32 +00:00
Default value: `5` .
### connect_timeout {#connect-timeout}
Connect timeout (in seconds).
Possible values:
2023-04-19 15:55:29 +00:00
- Positive integer.
2022-06-29 19:52:32 +00:00
Default value: `10` .
### read_write_timeout {#read-write-timeout}
Read/write timeout (in seconds).
Possible values:
2023-04-19 15:55:29 +00:00
- Positive integer.
2022-06-29 19:52:32 +00:00
Default value: `300` .
2020-03-20 10:10:48 +00:00
## See Also {#see-also}
2018-04-23 06:20:21 +00:00
2023-04-19 15:55:29 +00:00
- [The mysql table function ](../../../sql-reference/table-functions/mysql.md )
- [Using MySQL as a dictionary source ](../../../sql-reference/dictionaries/index.md#dictionary-sources#dicts-external_dicts_dict_sources-mysql )