Delivering data from an Data Streams queue to Managed Service for YDB

With Data Transfer, you can deliver data from a stream in Data Streams to a Managed Service for YDB database.

To transfer data:

1. Set up a data stream in Data Streams.
2. Set up and activate the transfer.
3. Test your transfer.

If you no longer need the resources you created, delete them.

Required paid resourcesRequired paid resources

The support cost includes:

• Fee for each Managed Service for YDB database. The charge depends on the usage mode:

  • For the serverless mode, you pay for data operations and the amount of stored data.
  • For the dedicated instance mode, you pay for the use of computing resources, dedicated DBs, and disk space.

  Learn more about the Managed Service for YDB pricing plans here.

• Data Streams fee, which depends on the pricing mode:

  • Provisioned capacity pricing mode: You pay for the number of write units and resources allocated for data streaming.
  • On-demand pricing mode:

    • If the DB operates in serverless mode, the data stream is charged according to the YDB serverless mode pricing policy.

    • If the DB operates in dedicated instance mode, the data stream is not charged separately (you only pay for the DB, see the pricing policy).

  Learn more about the Data Streams pricing plans here.

• Transfer fee: Using computing resources and the number of transferred data rows (see Data Transfer pricing).

Getting startedGetting started

Set up your data transfer infrastructure:

Create a data stream in Data StreamsCreate a data stream in Data Streams

Create a data stream in Data Streams.

Set up and activate the transferSet up and activate the transfer

1. Create a Data Streams source endpoint.

   • Database type: Yandex Data Streams.

   • Endpoint parameters:

     • Connection settings:

       • Database: Select the Managed Service for YDB database for the data stream in Data Streams from the list.
       • Stream: Specify the name of the stream in Data Streams.
       • Service account: Select or create a service account with the yds.editor role.

     • Advanced settings:

       • Conversion rules: JSON.

       • Data scheme: JSON specification.

         Fill in the data schema:

         Data schema

             [
                 {
                     "name": "device_id",
                     "type": "string"
                 },
                 {
                     "name": "datetime",
                     "type": "datetime"
                 },
                 {
                     "name": "latitude",
                     "type": "double"
                 },
                 {
                     "name": "longitude",
                     "type": "double"
                 },
                 {
                     "name": "altitude",
                     "type": "double"
                 },
                 {
                     "name": "speed",
                     "type": "double"
                 },
                 {
                     "name": "battery_voltage",
                     "type": "any"
                 },
                 {
                     "name": "cabin_temperature",
                     "type": "double"
                 },
                 {
                     "name": "fuel_level",
                     "type": "any"
                 }
             ]
         

2. Create a target endpoint:

   • Database type: YDB.

   • Endpoint parameters:

     • Connection settings:

       • Database: Select the Managed Service for YDB target database from the list.
       • Service account ID: Select or create a service account with the ydb.editor role.

3. Create a transfer:

   Manually

   Terraform

   1. Create a transfer of the Replication type that will use the created endpoints.
   2. Activate your transfer.

   1. In the yds-to-ydb.tf file, specify the values of the following variables:

      • source_endpoint_id: Source endpoint ID.
      • target_endpoint_id: Target endpoint ID.
      • transfer_enabled: Set to 1 to create a transfer.

   2. Make sure the Terraform configuration files are correct using this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

   3. Create the required infrastructure:

      1. Run this command to view the planned changes:

         terraform plan
         

         If 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.

      2. If everything looks correct, apply the changes:

         1. Run this command:

            terraform apply
            

         2. Confirm updating the resources.

         3. Wait for the operation to complete.

      The transfer will be activated automatically.

Test your transferTest your transfer

1. Wait for the transfer status to change to Replicating.

2. Send test data to the data stream in Data Streams:

   {
       "device_id":"iv9a94th6rzt********",
       "datetime":"2020-06-05T17:27:00",
       "latitude":"55.70329032",
       "longitude":"37.65472196",
       "altitude":"427.5",
       "speed":"0",
       "battery_voltage":"23.5",
       "cabin_temperature":"17",
       "fuel_level":null
   }
   

3. Make sure the data has moved to the target database:

   Management console

   YDB CLI

   1. In the management console, select the folder with the DB.
   2. In the list of services, select Managed Service for YDB.
   3. Select the database from the list.
   4. Navigate to the Navigation tab.
   5. Make sure the <stream_name> table now contains the test data.

   1. Connect to the Managed Service for YDB database.

   2. Make sure the <stream_name> table now contains the test data:

      ydb table query execute \
      --query "SELECT * \
      FROM <stream_name>"
      

Delete the resources you createdDelete the resources you created

Some resources are not free of charge. To avoid unnecessary charges, delete the resources you no longer need:

1. Delete the transfer.
2. Delete the source and target endpoints.
3. If you created any service accounts, delete them.

Delete the other resources depending on how you created them: