Loading data from Object Storage to a Greenplum® data mart
Note
You can migrate data from Object Storage to the Managed Service for Greenplum® table using Data Transfer. To do this:
- Prepare the test data.
- Create a database in the target cluster.
- Prepare and activate your transfer.
- Test your transfer.
If you no longer need the resources you created, delete them.
Required paid resources
The support cost for this solution includes:
- Fee for an Object Storage bucket: Covers data storage and bucket operations (see Object Storage pricing).
- Managed Service for Greenplum® cluster fee: using computing resources allocated to hosts and disk space (see Managed Service for Greenplum® pricing).
- Fee for public IP address assignment on cluster hosts (see Virtual Private Cloud pricing).
- Fee per transfer: Based on computational resource usage and the number of data rows transferred (see Data Transfer pricing).
Getting started
-
Set up the infrastructure:
ManuallyUsing Terraform-
Create a target Managed Service for Greenplum® cluster in any suitable configuration with publicly available hosts and the following settings:
- Username:
user1. - Password:
<user_password>.
- Username:
-
If using security groups in your cluster, make sure they are configured correctly and allow connecting to the cluster.
-
Create a service account named
storage-viewerwith thestorage.viewerrole. The transfer will use it to access the bucket. -
Create a static access key for the
storage-viewerservice account.
-
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 object-storage-to-greenplum.tf
configuration file to the same working directory.This file describes:
- Network.
- Subnet.
- Cluster access security group.
- Service account for bucket operations, e.g., creation and access.
- Yandex Lockbox secret for the service account static key required to configure the source endpoint.
- Source Object Storage bucket.
- Managed Service for Greenplum® target cluster.
- Transfer.
-
In the
object-storage-to-greenplum.tffile, specify the values of the following variables:folder_id: Cloud folder ID, same as in the provider settings.bucket_name: Bucket name consistent with the naming conventions.gp_version: Greenplum® version.gp_password: Greenplum® user password.
-
Make sure the Terraform configuration files are correct 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
. -
-
-
Enable the Access from Data Transfer option in the target cluster.
Prepare the test data
-
Prepare two CSV files with test data:
-
demo_data1.csv:1,Anna 2,Robert 3,Umar 4,Algul 5,Viktor -
demo_data2.csv:6,Maria 7,Alex
-
-
Upload the
demo_data1.csvfile to the Object Storage bucket.
Create a database in the target cluster
-
Connect to the auxiliary
postgresdatabase in the Managed Service for Greenplum® target cluster asuser1. -
Create a database named
db1:CREATE DATABASE db1;
Prepare and activate your transfer
-
Create an
Object Storage-type source endpoint with the following settings:-
Database type:
Object Storage. -
Bucket: Object Storage bucket name.
-
Access Key ID: Public component of the service account’s static key. If you created your infrastructure using Terraform, copy the key value from the Yandex Lockbox secret.
-
Secret Access Key: Service account’s secret access key. If you created your infrastructure using Terraform, copy the key value from the Yandex Lockbox secret.
-
Endpoint:
https://storage.yandexcloud.net. -
Region:
ru-central1. -
Data format:
CSV. -
Delimiter: Comma (
,). -
Table:
table1. -
Result table schema: Select
Manualand specify the following field names and data types:Id:Int64Name:UTF8
Leave the default values for the other properties.
-
-
Create a target endpoint of the
Greenplum®type and specify the cluster connection settings in it:- Connection type:
Managed Service for Greenplum cluster - Managed Service for Greenplum cluster:
<target_Greenplum®_cluster_name>from the drop-down list - Database:
db1 - User:
user1 - Password:
<user_password>.
- Connection type:
-
Create and activate your transfer:
ManuallyUsing Terraform-
Create a transfer of the Snapshot and replication type that will use the created endpoints.
-
Activate the transfer and wait for its status to change to Replicating.
-
In the
object-storage-to-greenplum.tffile, specify these variables:source_endpoint_id: Source endpoint ID.target_endpoint_id: Target endpoint ID.transfer_enabled:1to create a transfer.
-
Make sure the Terraform configuration files are correct 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. Wait for its status to change to Replicating.
-
Test the transfer
To verify that the transfer is operational, check the copy and replication processes.
Test the copy process
-
Connect to the
db1database in your target Managed Service for Greenplum® cluster. -
Run this request:
SELECT * FROM public.table1;Response example
__file_name | __row_index | Id | Name ---------------+-------------+----+-------- demo_data1.csv | 1 | 1 | Anna demo_data1.csv | 2 | 2 | Robert demo_data1.csv | 3 | 3 | Umar demo_data1.csv | 4 | 4 | Algul demo_data1.csv | 5 | 5 | Viktor
Test the replication process
-
Upload the
demo_data2.csvfile to the Object Storage bucket. -
Make sure the data from
demo_data2.csvhas been added to the target database:-
Connect to
db1in the Managed Service for Greenplum® target cluster. -
Run this request:
SELECT * FROM public.table1;Response example
__file_name | __row_index | Id | Name ---------------+-------------+----+-------- demo_data1.csv | 1 | 1 | Anna demo_data1.csv | 2 | 2 | Robert demo_data1.csv | 3 | 3 | Umar demo_data1.csv | 4 | 4 | Algul demo_data1.csv | 5 | 5 | Viktor demo_data2.csv | 1 | 6 | Maria demo_data2.csv | 2 | 7 | Alex
-
Delete the resources you created
Some resources incur charges. To avoid unnecessary expenses, delete the resources you no longer need:
-
Objects from the bucket
-
Delete other resources using the method matching their creation method:
ManuallyUsing Terraform-
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.
-
-