Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Data Transfer
  • Available transfers
  • Getting started
    • Resource relationships
    • Transfer types and lifecycles
    • What objects can be transferred
    • Regular incremental copy
    • Parallel copy
    • Data transformation
    • Serialization
    • Yandex Data Transfer specifics for sources and targets
    • Delivery guarantees
    • Operations on transfers
    • Networking in Yandex Data Transfer
    • Speed for copying data in Yandex Data Transfer
    • Change data capture
    • What tasks the service is used for
    • Quotas and limits
  • Troubleshooting
  • Access management
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials

In this article:

  • Processing empty objects
  • Processing VIEW objects
  • Processing complex data types
  1. Concepts
  2. What objects can be transferred

What objects can be transferred

Written by
Yandex Cloud
Updated at January 20, 2025
  • Processing empty objects
  • Processing VIEW objects
  • Processing complex data types

The main objects transferred are tables and data schemas.

In addition, certain types of endpoints support a transfer of empty objects or views. There are also limits on complex data types.

Processing empty objectsProcessing empty objects

You can only transfer non-empty tables and their data but not other schema elements (indexes, external keys, etc.) between endpoints of different types (e.g., from PostgreSQL to ClickHouse®).
Auto incremental fields are also transferred, but AUTO_INCREMENT is not.

For example, the following table

CREATE TABLE `sometable` (
`id` bigint UNSIGNED NOT NULL AUTO_INCREMENT

will be transferred as

CREATE TABLE "sometable" (
"id" int8 NOT NULL

Transfers between same-type endpoints (such as from PostgreSQL to PostgreSQL) transfer empty objects as part of a schema.

Processing VIEW objectsProcessing VIEW objects

In general, Yandex Data Transfer transfers VIEW objects (from databases where they may exist) with some restrictions:

  • Replication transfers do not replicate VIEW data changes.
  • Snapshot and Snapshot and increment transfers (in the copy step) between same-type endpoints, such as from PostgreSQL to PostgreSQL, only transfer a VIEW as part of a schema. VIEW data (rows) are not transferred. Schema transfers are configured by the Schema transfer setting and related settings available in some source endpoints.
  • Snapshot and Snapshot and increment transfers (in the copy step) between endpoints of different types, such as from PostgreSQL to ClickHouse®, transfer VIEW objects as regular tables and not as regular views. This feature allows converting and exporting data to external databases and can be helpful when making regular transfers of the Snapshot type.

Some sources may impose additional restrictions on transfers of VIEW and similar objects. For more information about how to work with views from particular sources, see Yandex Data Transfer specifics for sources and targets.

Processing complex data typesProcessing complex data types

In transfers between endpoints of different types (e.g., from PostgreSQL to ClickHouse®), it is not recommended to transfer data of complex types (e.g., arrays of numbers). Data Transfer does not support conversion of such data, because each DBMS has its own limitations and rules for data types. When using complex types, the transfer may not work correctly.

ClickHouse® is a registered trademark of ClickHouse, Inc.

Was the article helpful?

Previous
Transfer types and lifecycles
Next
Regular incremental copy
© 2025 Direct Cursus Technology L.L.C.