Transferring data to a Yandex Object Storage target endpoint

Yandex Data Transfer enables you to migrate data to the Yandex Object Storage storage and implement various data transfer, processing, and transformation scenarios. To implement a transfer:

1. Explore possible data transfer scenarios.
2. Configure one of the supported data sources.
3. Configure the target endpoint in Yandex Data Transfer.
4. Create a transfer and start it.
5. Perform required operations with the storage and control the transfer.
6. In case of any issues, use ready-made solutions to resolve them.

Scenarios for transferring data to Yandex Object StorageScenarios for transferring data to Yandex Object Storage

1. Data delivery is a process of delivering arbitrary data to target storage. It includes data retrieval from a queue and its deserialization with subsequent transformation to target storage format.

   • Delivering data from YDS to Object Storage.

2. Uploading data to scalable Object Storage storage allows you to save on data storage and simplifies the exchange with contractors.

   • Loading data from MySQL® to Object Storage.
   • Loading data from PostgreSQL to Object Storage.
   • Loading data from OpenSearch to Object Storage.
   • Loading data from Managed Service for YDB to Object Storage.

For a detailed description of possible Yandex Data Transfer scenarios, see Tutorials.

Configuring the data sourceConfiguring the data source

Configure one of the supported data sources:

• PostgreSQL
• MySQL®
• MongoDB
• Apache Kafka®
• Airbyte®
• YDS
• Oracle
• Managed Service for YDB
• Elasticsearch
• OpenSearch.

For a complete list of supported sources and targets in Yandex Data Transfer, see Available transfers.

Configuring the Object Storage target endpointConfiguring the Object Storage target endpoint

When creating or updating an endpoint, you can define:

• Configuration settings for an Yandex Object Storage bucket or custom S3-compatible storage.
• Additional parameters.

Bucket configurationsBucket configurations

Additional settingsAdditional settings

• Serialization format: Format in which the data will be written to the bucket: JSON, CSV, PARQUET, or Raw data. To learn more, see Serialization on delivery to Object Storage.

• Convert complex data to strings: Conversion of complex values to strings for JSON output format.

• Encoding format: Compression of output data (Gzip or Uncompressed).

• Buffer size: Size of files the data will be split into.

• Flush interval: Time after which the file will be written, regardless of its size.

• Folder name: Object folder name. It supports the data layout pattern by date. Example: 2006/01/02/<folder_name>.

• Time zone: Time zone according to which time the files are distributed. Only affects the distribution of files to folders in the bucket, but does not affect the data within the files.

• Row time column name: Column name to specify logical time for the data. The default value is the system recording time. When recording data to the target, the time is converted to UTC. This behavior cannot be changed.

After configuring the data source and target, create and start the transfer.

Troubleshooting data transfer issuesTroubleshooting data transfer issues

For more troubleshooting tips, see Troubleshooting.

Source data update errorSource data update error

Error message:

Push failed: kind: update not supported

Object Storage only supports inserting new data but does not support updating it. If data is updated at the source, the transfer will fail with the above error.

Solution: Use sources supporting data insertion only or select a target other than Object Storage.