Module schema_registry_converter::schema_registry[−][src]

Enums

Strategy similar to the one in the Java client. By default schema's needs to be backwards compatible. Historically the only available strategy was the TopicNameStrategy. This meant in practice that a topic could only have one type, or the restriction on backwards compatibility was to be abandoned. Using either of the two other strategies allows multiple types of schema on on topic, while still being able to keep the restriction on schema's being backwards compatible.

Functions

get_schema_by_id	Gets a schema by an id. This is used to get the correct schema te deserialize bytes, when the id is encoded in the bytes.
get_schema_by_subject	Gets the schema and the id by supplying a SubjectNameStrategy. This is used to correctly transform a vector to bytes.
get_subject	Gets the subject part which is also used as key to cache the results. It's constructed so that it's compatible with the Java client.