Loading data from Yandex Object Storage to Yandex Managed Service for YDB using Yandex Data Transfer
You can migrate data from Object Storage to the Managed Service for YDB table using Data Transfer. To do this:
If you no longer need the resources you created, delete them.
Getting started
Prepare the infrastructure:
-
Create a Managed Service for YDB database in any suitable configuration.
-
If you selected Dedicated DB mode, create and configure a security group in the network hosting the DB.
-
Create a service account named
s3-ydb-account
with thestorage.editor
andydb.editor
roles. The transfer will use it to access the bucket and the database. -
Create a static access key for
s3-ydb-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-ydb.tf
configuration file to the same working directory.This file describes:
- Service account to use when working with the Managed Service for YDB bucket and database.
- Yandex Lockbox secret which will store the static key of the service account to configure the source endpoint.
- Object Storage source bucket.
- Managed Service for YDB target cluster.
- Target endpoint.
- Transfer.
-
In the
object-storage-to-ydb.tf
file, 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.
-
Check that the Terraform configuration files are correct using this command:
terraform validate
If there are any errors in the configuration files, Terraform will point them out.
-
Create the required infrastructure:
-
Run the command to view planned changes:
terraform plan
If the resource configuration descriptions are correct, the terminal will display a list of the resources to modify and their parameters. This is a test step. No resources are updated.
-
If you are happy with the planned changes, apply them:
-
Run the command:
terraform apply
-
Confirm the update of 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 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.csv
file to the Object Storage bucket.
Prepare and activate the transfer
-
Create a source endpoint of the
Object Storage
type with the following settings:-
Database type:
Object Storage
. -
Bucket: Bucket name in Object Storage.
-
Access Key ID: Public part of the service account static key. If you created your infrastructure with Terraform, copy the key value from the Yandex Lockbox secret.
-
Secret Access Key: Private part of the service account static key. If you created your infrastructure with 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
Manual
and specify field names and data types:Id
:Int64
Name
:UTF8
Leave the default values for other properties.
-
-
Create a target endpoint and a transfer:
ManuallyUsing Terraform-
Create a target endpoint of the
YDB
type and specify the cluster connection parameters in it:- Database: Select the YDB database from the list.
- Service account ID: Select the
s3-ydb-account
service account.
-
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-ydb.tf
file, specify the following parameters:source_endpoint_id
: Source endpoint ID.transfer_enabled
:1
to create a transfer.
-
Check that the Terraform configuration files are correct using this command:
terraform validate
If there are any errors in the configuration files, Terraform will point them out.
-
Create the required infrastructure:
-
Run the command to view planned changes:
terraform plan
If the resource configuration descriptions are correct, the terminal will display a list of the resources to modify and their parameters. This is a test step. No resources are updated.
-
If you are happy with the planned changes, apply them:
-
Run the command:
terraform apply
-
Confirm the update of resources.
-
Wait for the operation to complete.
-
-
-
The transfer will be activated automatically. Wait for its status to change to Replicating.
-
Test the transfer
Check the transfer performance by testing the copy and replication processes.
Test the copy process
- In the management console
, select the folder with the DB you need. - In the list of services, select Managed Service for YDB.
- Select the database from the list.
- Go to the Navigation tab.
- Check that the Managed Service for YDB database contains a table named
table1
with the test data.
-
Run the following query:
SELECT * FROM table1;
Response example
Id | Name | __file_name | __row_index ---+----------+------------------+------------- 1 | "Anna" | "demo_data1.csv" | 1 2 | "Robert" | "demo_data1.csv" | 2 3 | "Umar" | "demo_data1.csv" | 3 4 | "Algul" | "demo_data1.csv" | 4 5 | "Viktor" | "demo_data1.csv" | 5
Test the replication process
-
Upload the
demo_data2.csv
file to the Object Storage bucket. -
Make sure the data from
demo_data2.csv
has been added to the target database:Management consoleCLI- In the management console
, select the folder with the DB you need. - In the list of services, select Managed Service for YDB.
- Select the database from the list.
- Go to the Navigation tab.
- Check that
table1
now contains the new data.
-
Run the following query:
SELECT * FROM table1;
Response example
Id | Name | __file_name | __row_index ---+----------+------------------+------------- 1 | "Anna" | "demo_data1.csv" | 1 2 | "Robert" | "demo_data1.csv" | 2 3 | "Umar" | "demo_data1.csv" | 3 4 | "Algul" | "demo_data1.csv" | 4 5 | "Viktor" | "demo_data1.csv" | 5 6 | "Maria" | "demo_data2.csv" | 1 7 | "Alex" | "demo_data2.csv" | 2
- In the management console
Delete the resources you created
Note
Before deleting the created resources, deactivate the transfer.
Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need:
-
Objects from the bucket.
-
Delete the other resources depending on how they were created:
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.
-
-