Migrating databases from Greenplum® to ClickHouse®
You can migrate a database from Greenplum® to ClickHouse® using Yandex Data Transfer.
To transfer a database from Greenplum® to ClickHouse®:
If you no longer need the resources you created, delete them.
Required paid resources
The support cost for this solution includes:
-
Yandex MPP Analytics for PostgreSQL cluster fee: Covers the use of computational resources allocated to hosts and disk storage (see Yandex MPP Analytics for PostgreSQL pricing).
-
Managed Service for ClickHouse® cluster fee: Covers the use of computational resources allocated to hosts (including ZooKeeper hosts) and disk storage (see Managed Service for ClickHouse® pricing).
-
Fee for public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).
-
Transfer fee: Based on computational resource consumption and the total number of data rows transferred (see Data Transfer pricing).
Getting started
In our example, we will create all required resources in Yandex Cloud. Set up the infrastructure:
-
Create a Yandex MPP Analytics for PostgreSQL source cluster with any suitable configuration.
-
Create a Yandex Managed Service for ClickHouse® target cluster with a database named
db1using any suitable configuration. -
If using security groups, make sure they are configured correctly and allow inbound connections to the clusters.
-
Create a
ClickHouse®target endpoint. In the endpoint settings, specifyDroporTruncateas the cleanup policy to prevent duplication of copied data.
-
If you do not have Terraform yet, install it.
-
Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.
-
Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it
. -
Place the configuration file in a separate working directory and specify the parameter values. If you did not add the authentication credentials to environment variables, specify them in the configuration file.
-
Download the greenplum-clickhouse.tf
configuration file to your current working directory.This file describes:
-
Security groups for cluster access.
-
Yandex MPP Analytics for PostgreSQL source cluster.
-
Managed Service for ClickHouse® target cluster.
-
Target endpoint.
-
In the
greenplum-clickhouse.tffile, specify the following:mgp_password: Greenplum® admin password.mch_db: ClickHouse® database name.mch_user: ClickHouse® database user name.mch_password: ClickHouse® database user password.
-
Validate your Terraform configuration files using this command:
terraform validateTerraform will display any configuration errors detected in your files.
-
Create the required infrastructure:
-
Run this command to view the planned changes:
terraform planIf you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.
-
If everything looks correct, apply the changes:
-
Run this command:
terraform apply -
Confirm updating the resources.
-
Wait for the operation to complete.
-
All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console
. -
Set up your transfer
-
Create a
Greenplum®source endpoint and specify its cluster connection settings. -
Create a Snapshot transfer that uses endpoints for the source and target.
While real-time replication is not supported for this endpoint pair, you can configure regular copying while creating the transfer. To do this, in the Transfer parameters field under Snapshot, select Regular and specify the copy interval. The transfer will automatically activate after the specified interval.
Activate the transfer
-
Connect to the Yandex MPP Analytics for PostgreSQL cluster, create a table named
x_tab, and populate it with data:CREATE TABLE x_tab ( id NUMERIC, name CHARACTER(5) ); CREATE INDEX ON x_tab (id); INSERT INTO x_tab (id, name) VALUES (40, 'User1'), (41, 'User2'), (42, 'User3'), (43, 'User4'), (44, 'User5'); -
Activate the transfer and wait for its status to change to Completed.
-
To verify the data transfer, connect to the Managed Service for ClickHouse® target cluster and check whether the columns of the
x_tabtable in thedb1database match those of thex_tabtable in the source database:SELECT id, name FROM db1.x_tab;┌─id─┬─name──┐ │ 40 │ User1 │ │ 41 │ User2 │ │ 42 │ User3 │ │ 43 │ User4 │ │ 44 │ User5 │ └────┴───────┘
Verify replication after reactivation
-
Connect to the Yandex MPP Analytics for PostgreSQL cluster. Then, in the
x_tabtable, delete one row and update another:DELETE FROM x_tab WHERE id = 41; UPDATE x_tab SET name = 'Key3' WHERE id = 42; -
Reactivate the transfer and wait for its status to change to Completed.
-
Make sure the changes have been applied to the
x_tabtable on the ClickHouse® target:SELECT id, name FROM db1.x_tab;┌─id─┬─name──┐ │ 42 │ Key3 │ │ 40 │ User1 │ │ 43 │ User4 │ │ 44 │ User5 │ └────┴───────┘
Delete the resources you created
Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need:
-
Make sure the transfer status is Completed, upon which you can delete the transfer.
-
Delete other resources using the same method used for their creation:
ManuallyTerraform- Delete the Managed Service for ClickHouse® cluster.
- Delete the Yandex MPP Analytics for PostgreSQL cluster.
- Delete the target endpoint.
-
In the terminal window, go to the directory containing the infrastructure plan.
Warning
Make sure the directory has no Terraform manifests with the resources you want to keep. Terraform deletes all resources that were created using the manifests in the current directory.
-
Delete resources:
-
Run this command:
terraform destroy -
Confirm deleting the resources and wait for the operation to complete.
All the resources described in the Terraform manifests will be deleted.
-
ClickHouse® is a registered trademark of ClickHouse, Inc