Working with Managed Service for ClickHouse® databases
This section covers the basics of working with Managed Service for ClickHouse®.
To start working with a Managed Service for ClickHouse® database, follow these steps:
- Create a connection containing your database access credentials.
- Run a query against the database
An example of a query that reads data from Managed Service for ClickHouse®:
SELECT * FROM clickhouse_mdb_connection.my_table
Where:
clickhouse_mdb_connection: Your database connection name.my_table: Database table name.
Setting up a connection
To create a connection to Managed Service for ClickHouse®:
-
In the management console
, select the folder where you want to create your connection. -
Navigate to Yandex Query.
-
In the left-hand panel, navigate to the Connections tab.
-
Click
Create new. -
Specify the connection settings:
-
Under General parameters:
- Name: Managed Service for ClickHouse® connection name.
- Type:
Managed Service for ClickHouse.
-
Under Connection type parameters:
-
Cluster: Select an existing Managed Service for ClickHouse® cluster or create a new one.
-
Service account: Select an existing Managed Service for ClickHouse® service account or create a new one. Assign it the
managed-clickhouse.viewerrole allowing it to connect toManaged Service for ClickHouse®clusters.To use a service account, the
iam.serviceAccounts.userrole is required. -
Database: Select the database you will use when working with the ClickHouse® cluster.
-
Login: Username you will use to connect to ClickHouse® databases.
-
Password: Password you will use to connect to ClickHouse® databases.
-
-
-
Click Create.
A service account is necessary to detect Managed Service for ClickHouse® cluster connection endpoints inside Yandex Cloud. To access data, you need a separate username and password.
Warning
First, grant network access from Yandex Query to Managed Service for ClickHouse® clusters. To do this, enable Yandex Query access in your target database settings.
Query syntax
ClickHouse® uses the following SQL syntax:
SELECT * FROM <connection>.<table_name>
Where:
<connection>: Your database connection name.<table_name>: Database table name.
Limitations
Working with ClickHouse® clusters comes with certain limitations.
The following limitations apply:
-
External sources are only available for data reading through
SELECTrequests. Yandex Query does not currently support requests that modify tables in external sources. - YQ uses the Yandex Managed Service for YDB type system
. However, the valid value ranges for YDB date and time types, i.e.,Date,Datetime, andTimestamp, are often too narrow to accommodate the values of the corresponding ClickHouse® types, i.e.,Date,Date32,Datetime, andDatetime64.
As a result, when reading date and time values from ClickHouse®, YQ returns them as plain strings (typeUtf8for regular columns orOptional<Utf8>for nullable columns) in ISO-8601 format.
Filter pushdown
Yandex Query can transfer processing of request parts to the data source system. This means that filter expressions are provided through Yandex Query directly to the database for processing; these are typically the query conditions specified in WHERE. This kind of processing is called filter pushdown.
Filter pushdown is possible when using:
| Description | Example |
|---|---|
NULL check |
WHERE column1 IS NULL or WHERE column1 IS NOT NULL |
OR, NOT, or AND logical conditions or parentheses to prioritize calculations |
WHERE column1 IS NULL OR (column2 IS NOT NULL AND column3 > 10). |
Comparison operators (=, ==, !=, <>, >, <, >=, or <=) to other columns or constants |
WHERE column1 > column2 OR column3 <= 10, WHERE column1 + column2 > 10, WHERE column1 = (10 + 10) |
Other filter types do not support source pushdown: the external table rows will be filtered on the federated Yandex Query side, i.e., Yandex Query will perform a full scan of the external table when processing the query.
Supported data types for filter pushdown:
| Data type Yandex Query |
|---|
Bool |
Int8 |
Uint8 |
Int16 |
Uint16 |
Int32 |
Uint32 |
Int64 |
Uint64 |
Float |
Double |
String |
Supported data types
By default, columns in ClickHouse® cannot physically contain NULL values. However, you can create a table with columns of optional or nullable
The tables below show type mapping between ClickHouse® and Yandex Query. Only the data types listed are supported.
Primitive data types
| ClickHouse® data type | Yandex Query data type | Notes |
|---|---|---|
Bool |
Bool |
|
Int8 |
Int8 |
|
UInt8 |
Uint8 |
|
Int16 |
Int16 |
|
UInt16 |
Uint16 |
|
Int32 |
Int32 |
|
UInt32 |
Uint32 |
|
Int64 |
Int64 |
|
UInt64 |
Uint64 |
|
Float32 |
Float |
|
Float64 |
Double |
|
Date |
Utf8 |
|
Date32 |
Utf8 |
|
DateTime |
Utf8 |
|
DateTime64 |
Utf8 |
|
String |
String |
|
FixedString |
String |
Null FixedString bytes are transferred to String unchanged. |
Optional data types
| ClickHouse® data type | Yandex Query data type | Notes |
|---|---|---|
Nullable(Bool) |
Optional<Bool> |
|
Nullable(Int8) |
Optional<Int8> |
|
Nullable(UInt8) |
Optional<Uint8> |
|
Nullable(Int16) |
Optional<Int16> |
|
Nullable(UInt16) |
Optional<Uint16> |
|
Nullable(Int32) |
Optional<Int32> |
|
Nullable(UInt32) |
Optional<Uint32> |
|
Nullable(Int64) |
Optional<Int64> |
|
Nullable(UInt64) |
Optional<Uint64> |
|
Nullable(Float32) |
Optional<Float> |
|
Nullable(Float64) |
Optional<Double> |
|
Nullable(Date) |
Optional<Utf8> |
|
Nullable(Date32) |
Optional<Utf8> |
|
Nullable(DateTime) |
Optional<Utf8> |
|
Nullable(DateTime64) |
Optional<Utf8> |
|
Nullable(String) |
Optional<String> |
|
Nullable(FixedString) |
Optional<String> |
Null FixedString bytes are transferred to String unchanged. |
ClickHouse® is a registered trademark of ClickHouse, Inc