Copying data from Managed Service for OpenSearch to Yandex MPP Analytics for PostgreSQL using Yandex Data Transfer
With Data Transfer, you can transfer data from a Managed Service for OpenSearch source cluster to a Greenplum® target cluster in Yandex MPP Analytics for PostgreSQL.
To transfer data:
- Get your cloud ready.
- Set up your infrastructure.
- Prepare your test data.
- Set up and activate the transfer.
- Test your transfer.
If you no longer need the resources you created, delete them.
Get your cloud ready
Sign up for Yandex Cloud and create a billing account:
- Navigate to the management console
and log in to Yandex Cloud or create a new account. - On the Yandex Cloud Billing
page, make sure you have a billing account linked and it has theACTIVEorTRIAL_ACTIVEstatus. If you do not have a billing account, create one and link a cloud to it.
If you have an active billing account, you can navigate to the cloud page
Learn more about clouds and folders here.
Required paid resources
- Managed Service for OpenSearch cluster: Use of computing resources and storage size (see Managed Service for OpenSearch pricing).
- Yandex MPP Analytics for PostgreSQL cluster: Computing resources allocated to hosts, storage and backup size (see Yandex MPP Analytics for PostgreSQL pricing).
- Public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).
Set up your infrastructure
- Create a Managed Service for OpenSearch source cluster using any suitable configuration with publicly accessible hosts.
- In the same availability zone, create a Greenplum® target cluster in any suitable configuration. When creating a cluster:
- Enable public access for the hosts.
- Enable Data Transfer access.
- Get an SSL certificate to connect to the Managed Service for OpenSearch cluster.
- Make sure the Managed Service for OpenSearch and Greenplum® cluster security groups allow connecting from the internet.
-
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 opensearch-to-greenplum.tf
configuration file to the same working directory.This file describes:
- Network.
- Subnet.
- Security group and rules allowing inbound connections to the OpenSearch and Greenplum® clusters.
- Managed Service for OpenSearch source cluster and its
adminaccount. - Greenplum® target cluster in Yandex MPP Analytics for PostgreSQL.
- Transfer.
-
In the
opensearch-to-greenplum.tffile, specify the following settings:-
mos_cluster_name: Managed Service for OpenSearch cluster name. -
mos_version: OpenSearch version. -
mos_admin_password: Managed Service for OpenSearch clusteradminpassword. -
mgp_cluster_name: Greenplum® cluster name. -
mgp_username: Greenplum® cluster user name. -
mgp_user_password: Greenplum® cluster user password. -
transfer_name: Data Transfer transfer name. -
profile_name: Your YC CLI profile name.If you do not have the Yandex Cloud CLI installed yet, install and initialize it.
-
-
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
. -
Prepare your test data
-
In the source cluster, create a test index named
peopleand define its schema:curl --cacert ~/.opensearch/root.crt \ --user <source_cluster_user_name>:<source_cluster_user_password> \ --header 'Content-Type: application/json' \ --request PUT 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people' && \ curl --cacert ~/.opensearch/root.crt \ --user <source_cluster_user_name>:<source_cluster_user_password> \ --header 'Content-Type: application/json' \ --request PUT 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people/_mapping?pretty' -d' { "properties": { "name": {"type": "text"}, "age": {"type": "integer"} } } ' -
Populate the test index with data:
curl --cacert ~/.opensearch/root.crt \ --user <source_cluster_user_name>:<source_cluster_user_password> \ --header 'Content-Type: application/json' \ --request POST 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people/_doc/?pretty' -d' { "name": "Alice", "age": "30" } ' && \ curl --cacert ~/.opensearch/root.crt \ --user <source_cluster_user_name>:<source_cluster_user_password> \ --header 'Content-Type: application/json' \ --request POST 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people/_doc/?pretty' -d' { "name": "Robert", "age": "32" } ' -
Make sure the data is saved in the test index:
curl --cacert ~/.opensearch/root.crt \ --user <username_in_target_cluster>:<user_password_in_target_cluster> \ --header 'Content-Type: application/json' \ --request GET 'https://<address_of_OpenSearch_host_with_DATA_role>:9200/people/_search?pretty'
Set up and activate the transfer
-
Create a source endpoint for your pre-configured Managed Service for OpenSearch cluster using the following settings:
- Database type:
OpenSearch. - Connection settings:
- Connection type:
Managed Service for OpenSearch cluster. - Managed Service for OpenSearch cluster: Select the Managed Service for OpenSearch cluster from the list.
- User:
admin. - Password:
adminpassword.
- Connection type:
- Database type:
-
Create a target endpoint for the Greenplum® cluster you created earlier, with the following settings:
- Database type:
Greenplum. - Endpoint parameters:
- Connection type: Select
Managed Service for Greenplum cluster. - Managed Service for Greenplum cluster: Select the Greenplum® cluster from the list.
- Database:
postgres. - User: Enter the Greenplum® cluster user name.
- Password: Enter the Greenplum® cluster user password.
- Connection type: Select
- Database type:
-
Create a transfer:
ManuallyTerraform-
In the
opensearch-to-greenplum.tffile, specify the following settings:source_endpoint_id: Source endpoint ID.target_endpoint_id: Target endpoint ID.transfer_enabled:1to create a transfer.
-
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.
-
The transfer will activate automatically upon creation.
-
-
Test your transfer
-
Wait for the transfer status to change to Completed.
-
Make sure the data from the source Managed Service for OpenSearch cluster has been migrated to the Yandex MPP Analytics for PostgreSQL cluster:
-
Get an SSL certificate to connect to the Greenplum® cluster.
-
Install the dependencies:
sudo apt update && sudo apt install --yes postgresql-client -
Connect to the database in the Greenplum® cluster.
-
Check that the database contains the
peopletable populated with test data:SELECT * FROM people;
-
Delete the resources you created
To reduce the consumption of resources you do not need, delete them:
-
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.
-