Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • 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
© 2025 Direct Cursus Technology L.L.C.
Yandex MetaData Hub
  • About Yandex MetaData Hub
    • Getting started
        • Creating a namespace
        • 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 August 25, 2025

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. Select 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 the Confluent documentation.
    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
Editing a namespace
© 2025 Direct Cursus Technology L.L.C.