Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Query
    • Managing connections
    • Managing bindings
    • Uploading a schema
    • Managing queries
    • Connecting via an IDE
  • Access management
  • Pricing policy
  • Integrations
  • Audit Trails events
  • FAQ

In this article:

  • Data schemas
  • Plain text
  • JSON
  • Data Transfer-compatible JSON format
  1. Step-by-step guides
  2. Uploading a schema

Uploading a data schema

Written by
Yandex Cloud
Updated at July 7, 2026
View in Markdown
  • Data schemas
    • Plain text
    • JSON
    • Data Transfer-compatible JSON format

To streamline the repetitive steps when configuring schemas for data bindings, you can prepare a file with schemas and then upload it. To do this, follow these steps:

  1. In the management console, select the folder containing the data binding you want to update.
  2. Navigate to Yandex Query.
  3. In the left-hand panel, select Bindings.
  4. Locate the binding you need in the list, click in its row, and select Edit.
  5. Click Upload from file and select your schema file.
  6. Click Modify.

Data schemasData schemas

We support multiple schema formats:

  1. Plain text.
  2. JSON.
  3. JSON compatible with Data Transfer.

Plain textPlain text

The plain-text schema format is very similar to the SQL DDL syntax: it includes the SCHEMA keyword, a list of fields, and their corresponding data types. This is the only export format for data schemas in Yandex Query.

Here is an example of a schema in plain-text format:

SCHEMA=(
    billing_account_id String NOT NULL,
    billing_account_name String
    )

Where:

  • billing_account_id: Field name.
  • String: Field type.
  • NOT NULL: Flag indicating a required field in the source data.

JSONJSON

JSON format is used for importing schemas from external systems. A schema in JSON format is a set of properties defining field names, data types, and required flags.

Here is an example of a schema in JSON format:

[
    {
        "name": "billing_account_id",
        "type": "String",
        "required": true
    },
    {
        "name": "billing_account_name",
        "type": "String",
        "required": false
    }
]

Where:

  • billing_account_id: Field name.
  • String: Field type.
  • required: true: Flag indicating a required field in the source data.

Data Transfer-compatible JSON formatData Transfer-compatible JSON format

This format is intended for compatible description of data schemas across various systems. This JSON format consists of a set of records defining fields and their types, with all fields considered optional in the source data.

Schema example:

[
    {
        "name": "billing_account_id",
        "typeName": "String"
    },
    {
        "name": "billing_account_name",
        "typeName": "String"
    }
]

Where:

  • billing_account_id: Field name.
  • String: Field type.

To ensure compatibility between Yandex Query and Data Transfer, we recommend using the following data types:

  • INT64
  • INT32
  • INT16
  • UINT64
  • UINT32
  • UINT16
  • DOUBLE
  • STRING
  • UTF8

Was the article helpful?

Previous
Managing bindings
Next
Managing queries
© 2026 Direct Cursus Technology L.L.C.