Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article describes important Schema Registry limitations to consider when you design a streaming solution.
Limitations
- You can only create schema definitions by using the Avro 1.12 schema format.
- Schema-aware Eventstreams (preview) limits the maximum schema name to 50 characters. When the schema name exceeds this limit, Eventstreams can't process events with that schema.
- Decimal precision is limited to 28 digits. Messages containing decimal values with a precision greater than 28 digits are rejected during deserialization and aren't processed.
- No schema compatibility enforcement. Schema compatibility modes aren't enforced. You can make changes to a schema that might break your pipelines. You're responsible for ensuring schema updates don't negatively affect your data flows.
- Nonconforming events are dropped. Each Fabric feature that integrates with SchemaSet decides how to handle nonconforming events, but in general, only events that conform to an associated schema can pass through. To preserve data quality and integrity, Eventstream drops events that don't match the specified schema.
Validation errors appear in the Eventstream runtime logs. To inspect the errors, open the Eventstream item details pane, select the source node, and then select Runtime logs on the lower pane.