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
    • Service roles for access management
    • Troubleshooting
  • Access management
  • Quotas and limits
  • Pricing policy
  • Public materials
  • Release notes
  1. Schema Registry
  2. Troubleshooting

Troubleshooting in Yandex Schema Registry

Written by
Yandex Cloud
Updated at August 25, 2025

This section describes issues you may encounter in the service and how to troubleshoot them.

Error when adding or deleting optional parametersError when adding or deleting optional parameters

If a Confluent compatibility check policy is configured at the namespace level, the following errors may occur when adding or deleting optional parameters in the schema:

  • PROPERTY_ADDED_TO_OPEN_CONTENT_MODEL
  • PROPERTY_REMOVED_FROM_CLOSED_CONTENT_MODEL

Solution
The Confluent compatibility check policy is based on the Confluent Schema Registry standards and implements mathematically accurate compatibility checks. This policy does not allow adding or removing optional parameters in object fields, causing the errors mentioned above.

To add or delete optional parameters, select the optional-friendly JSON compatibility check policy in the namespace. It is based on using various content models for the producer and the consumer, where only the producer schema is registered. The compatibility check involves converting the consumer schema from an open content model to a closed one and comparing it with the registered producer schemas. This enables you to add or remove optional parameters while maintaining full transitive compatibility.

Was the article helpful?

Previous
Service roles for access management
Next
API authentication
© 2025 Direct Cursus Technology L.L.C.