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 MetaData Hub
  • About Yandex MetaData Hub
    • Getting started
        • Creating a namespace
        • Viewing a list of namespaces
        • Editing a namespace
        • Connecting to a namespace
        • Deleting a namespace
    • Service roles for access management
    • Troubleshooting
  • Access management
  • Quotas and limits
  • Pricing policy
  • Public materials
  • Release notes
  1. Schema Registry
  2. Step-by-step guides
  3. Namespace
  4. Creating a namespace

Creating a namespace

Written by
Yandex Cloud
Updated at July 29, 2026
View in Markdown

Note

This feature is at the Preview stage.

Management console
  1. In the management console, select the folder you want to create a connection in.
  2. Navigate to Yandex MetaData Hub.
  3. In the left-hand panel, select Schema Registry.
  4. Click Create a namespace.
  5. In the Name field, set a unique name for the namespace.
  6. Optionally, add a namespace description.
  7. Under Compatibility parameters:
    1. Set Compatibility check level:
      • BACKWARD: (Default) Consumers using the new schema can read data written by producers using the latest registered schema.
      • BACKWARD_TRANSITIVE: Consumers using the new schema can read data written by producers using all previously registered schemas.
      • FORWARD: Consumers using the latest registered schema can read data written by producers using the new schema.
      • FORWARD_TRANSITIVE: Consumers using all previously registered schemas can read data written by producers using the new schema.
      • FULL: New schema is forward and backward compatible with the latest registered schema.
      • FULL_TRANSITIVE: New schema is forward and backward compatible with all previously registered schemas.
      • NONE: Schema compatibility checks are disabled.
        For more information about schema compatibility types, see this Confluent guide.
    2. Select a compatibility policy for JSON schemas:
      • optional-friendly: Based on a solution using various content models for the producer and the consumer. It supports adding or removing optional parameters while maintaining full transitive compatibility.
      • Confluent: Follows the Confluent Schema Registry standards and ensures no full compatibility when adding and removing optional parameters.
    3. Select a compatibility policy for Protobuf schemas:
      • Confluent: Based on the Confluent Schema Registry standards.
      • buf: Based on the Buf v1 standards.
  8. Click Create.

Was the article helpful?

Previous
Getting started
Next
Viewing a list of namespaces
© 2026 Direct Cursus Technology L.L.C.