Loading data from Object Storage to a YDB data mart
Note
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.
Required paid resources
The support cost for this solution includes:
-
Object Storage bucket fee covering data storage and data operations (see Object Storage pricing).
-
Per-transfer fee: use of computing resources and number of transferred data rows (see Data Transfer pricing).
-
Managed Service for YDB database fee. Pricing is based on the deployment model:
- In serverless mode, you pay for data operations and storage volume.
- In dedicated instance mode, you pay for computing resource usage, dedicated databases, and disk storage.
For details, see Managed Service for YDB pricing.
Getting started
Set up 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-accountwith thestorage.editorandydb.editorroles. The transfer will use it to access the bucket and database. -
Create a static access key for the
s3-ydb-accountservice 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.
- Source Object Storage bucket.
- Target Managed Service for YDB cluster.
- Target endpoint.
- Transfer.
-
In the
object-storage-to-ydb.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.
-
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
. -
Prepare your 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.
Set up and activate the 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
Keep the default values for all other settings.
-
-
Create a target endpoint and set up the transfer:
ManuallyUsing Terraform-
Create a target endpoint of the
YDBtype and specify the cluster connection settings in it:-
Database: Select the YDB database from the list.
-
Service account ID: Select the service account named
s3-ydb-account.
-
-
Create a transfer of the Snapshot and replication type that will use the new endpoints.
-
Activate the transfer and wait for its status to change to Replicating.
-
In the
object-storage-to-ydb.tffile, specify the following settings:source_endpoint_id: Source endpoint ID.transfer_enabled:1(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, test the copy and replication processes.
Test the copy process
- In the management console
, select the folder with the DB you need. - From the list of services, select Managed Service for YDB.
- Select the database from the list.
- Navigate to the Navigation tab.
- Make sure the Managed Service for YDB database contains a table named
table1with the test data.
-
Run this 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.csvfile to the Object Storage bucket. -
Make sure the data from
demo_data2.csvhas been added to the target database:Management consoleCLI- In the management console
, select the folder with the DB you need. - From the list of services, select Managed Service for YDB.
- Select the database from the list.
- Navigate to the Navigation tab.
- Make sure
table1now contains the new data.
-
Run this 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 resources, deactivate the transfer.
Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need:
-
Bucket objects.
-
Delete other resources using the same method used for their creation:
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.
-
-