Docs Cloud Redpanda Connect Components Processors schema_registry_decode schema_registry_decode Available in: Cloud, Self-Managed Automatically decodes and validates messages with schemas from a Confluent Schema Registry service. This processor uses the Franz Kafka Schema Registry client. Common Advanced # Common configuration fields, showing default values label: "" schema_registry_decode: avro: raw_unions: false # No default (optional) preserve_logical_types: false cache_duration: 10m url: "" # No default (required) # All configuration fields, showing default values label: "" schema_registry_decode: avro: raw_unions: false preserve_logical_types: false mapping: "" # No default (optional) cache_duration: 10m url: "" # No default (required) oauth: enabled: false consumer_key: "" # Optional consumer_secret: "" # Optional access_token: "" # Optional access_token_secret: "" # Optional basic_auth: enabled: false username: "" # Optional password: "" # Optional jwt: enabled: false private_key_file: "" # Optional signing_method: "" # Optional claims: {} headers: {} tls: skip_cert_verify: false enable_renegotiation: false root_cas: "" # Optional root_cas_file: "" # Optional client_certs: [] Decodes messages automatically from a schema stored within a Confluent Schema Registry service by extracting a schema ID from the message and obtaining the associated schema from the registry. If a message fails to match against the schema then it will remain unchanged and the error can be caught using error-handling methods. Avro, Protobuf and JSON schemas are supported, all are capable of expanding from schema references as of v4.22.0. Avro JSON format By default, this processor expects documents formatted as Avro JSON when decoding with Avro schemas. In this format, the value of a union is encoded in JSON as follows: If the union’s type is null, it is encoded as a JSON null. Otherwise, the union is encoded as a JSON object with one name/value pair. The name is the type’s name, and the value is the recursively-encoded value. The user-specified name is used for Avro’s named types (record, fixed, or enum). For other types, the type name is used. For example, the union schema ["null","string","Transaction"], where Transaction is a record name, would encode: null as a JSON null The string "a" as {"string": "a"} A Transaction instance as {"Transaction": {…}}, where {…} indicates the JSON encoding of a Transaction instance Alternatively, you can create documents in standard/raw JSON format by setting the field avro.raw_unions to true. Protobuf format This processor decodes Protobuf messages to JSON documents. For more information about the JSON mapping of Protobuf messages, see the Protocol Buffers documentation. Metadata This processor adds the following metadata to processed messages: schema_id: The ID of the schema in the schema registry associated with the message. Fields avro Configuration for how to decode schemas that are of type AVRO. Type: object avro.mapping Define a custom mapping to apply to the JSON representation of Avro schemas. You can use mappings to convert custom types emitted by other tools, such as Debezium, into standard Avro types. Type: string # Examples: mapping: |- map isDebeziumTimestampType { root = this.type == "long" && this."connect.name" == "io.debezium.time.Timestamp" && !this.exists("logicalType") } map debeziumTimestampToAvroTimestamp { let mapped_fields = this.fields.or([]).map_each(item -> item.apply("debeziumTimestampToAvroTimestamp")) root = match { this.type == "record" => this.assign({"fields": $mapped_fields}) this.type.type() == "array" => this.assign({"type": this.type.map_each(item -> item.apply("debeziumTimestampToAvroTimestamp"))}) # Add a logical type so that it's decoded as a timestamp instead of a long. this.type.type() == "object" && this.type.apply("isDebeziumTimestampType") => this.merge({"type":{"logicalType": "timestamp-millis"}}) _ => this } } root = this.apply("debeziumTimestampToAvroTimestamp") avro.preserve_logical_types Choose whether to: Transform logical types into their primitive type (default). For example, decimals become raw bytes and timestamps become plain integers. Preserve logical types. Set to true to preserve logical types. Type: bool Default: false avro.raw_unions Whether Avro messages should be decoded into normal JSON (JSON that meets the expectations of regular internet JSON) rather than Avro JSON. If set to false, Avro messages are decoded as Avro JSON. For example, the union schema ["null","string","Transaction"], where Transaction is a record name, would be decoded as: A null as a JSON null The string "a" as {"string": "a"} A Transaction instance as {"Transaction": {…}}, where {…} indicates the JSON encoding of a Transaction instance. If set to true, Avro messages are decoded as standard JSON. For example, the same union schema ["null","string","Transaction"] is decoded as: A null as JSON null The string "a" as "a" A Transaction instance as {…}, where {…} indicates the JSON encoding of a Transaction instance. For more details on the difference between standard JSON and Avro JSON, see the comment in Goavro and the underlying library used for Avro serialization. Type: bool avro.translate_kafka_connect_types Only valid if preserve_logical_types is true. This decodes various Kafka Connect types into their bloblang equivalents when not representable by standard logical types according to the Avro standard. Types that are currently translated: Table 1. Debezium Custom Temporal Types Type Name Bloblang Type Description io.debezium.time.Date timestamp Date without time (days since epoch) io.debezium.time.Timestamp timestamp Timestamp without timezone (milliseconds since epoch) io.debezium.time.MicroTimestamp timestamp Timestamp with microsecond precision io.debezium.time.NanoTimestamp timestamp Timestamp with nanosecond precision io.debezium.time.ZonedTimestamp timestamp Timestamp with timezone (ISO-8601 format) io.debezium.time.Year timestamp at January 1st at 00:00:00 Year value io.debezium.time.Time timestamp at the unix epoch Time without date (milliseconds past midnight) io.debezium.time.MicroTime timestamp at the unix epoch Time with microsecond precision io.debezium.time.NanoTime timestamp at the unix epoch Time with nanosecond precision Type: bool Default: false basic_auth Allows you to specify basic authentication. Type: object basic_auth.enabled Whether to use basic authentication in requests. Type: bool Default: false basic_auth.password A password to authenticate with. This field contains sensitive information that usually shouldn’t be added to a configuration directly. For more information, see Manage Secrets before adding it to your configuration. Type: string Default: "" basic_auth.username A username to authenticate as. Type: string Default: "" cache_duration The duration after which a cached schema is considered stale and is removed from the cache. Type: string Default: 10m # Examples: cache_duration: 1h cache_duration: 5m jwt BETA: Allows you to specify JSON Web Token (JWT) authentication. Type: object jwt.claims A value used to identify the claims that issued the JWT. Type: object Default: {} jwt.enabled Whether to use JWT authentication in requests. Type: bool Default: false jwt.headers Add key/value headers to the JWT (optional). Type: object Default: {} jwt.private_key_file A file with the PEM encoded using PKCS1 or PKCS8 as private key. Type: string Default: "" jwt.signing_method A method used to sign the token, such as RS256, RS384, RS512 or EdDSA. Type: string Default: "" oauth Allows you to specify open authentication using OAuth version 1. Type: object oauth.access_token A value used to gain access to the protected resources on behalf of the user. Type: string Default: "" oauth.access_token_secret A secret provided in order to establish ownership of a given access token. This field contains sensitive information that usually shouldn’t be added to a configuration directly. For more information, see Manage Secrets before adding it to your configuration. Type: string Default: "" oauth.consumer_key A value used to identify the client to the service provider. Type: string Default: "" oauth.consumer_secret A secret used to establish ownership of the consumer key. This field contains sensitive information that usually shouldn’t be added to a configuration directly. For more information, see Manage Secrets before adding it to your configuration. Type: string Default: "" oauth.enabled Whether to use OAuth version 1 in requests. Type: bool Default: false protobuf Configuration for how to decode schemas that are of type PROTOBUF. Type: object protobuf.emit_default_values Whether to emit default-valued primitive fields, empty lists, and empty maps. emit_unpopulated takes precedence over emit_default_values Type: bool Default: false protobuf.emit_unpopulated Whether to emit unpopulated fields. It does not emit unpopulated oneof fields or unpopulated extension fields. Type: bool Default: false protobuf.use_enum_numbers Emits enum values as numbers. Type: bool Default: false protobuf.use_proto_names Use proto field name instead of lowerCamelCase name. Type: bool Default: false tls Custom TLS settings can be used to override system defaults. Type: object tls.client_certs[] A list of client certificates to use. For each certificate either the fields cert and key, or cert_file and key_file should be specified, but not both. Type: object Default: [] # Examples: client_certs: - cert: foo key: bar - cert_file: ./example.pem key_file: ./example.key tls.client_certs[].cert A plain text certificate to use. Type: string Default: "" tls.client_certs[].cert_file The path of a certificate to use. Type: string Default: "" tls.client_certs[].key A plain text certificate key to use. This field contains sensitive information that usually shouldn’t be added to a configuration directly. For more information, see Manage Secrets before adding it to your configuration. Type: string Default: "" tls.client_certs[].key_file The path of a certificate key to use. Type: string Default: "" tls.client_certs[].password A plain text password for when the private key is password encrypted in PKCS#1 or PKCS#8 format. The obsolete pbeWithMD5AndDES-CBC algorithm is not supported for the PKCS#8 format. Because the obsolete pbeWithMD5AndDES-CBC algorithm does not authenticate the ciphertext, it is vulnerable to padding oracle attacks that can let an attacker recover the plaintext. This field contains sensitive information that usually shouldn’t be added to a configuration directly. For more information, see Manage Secrets before adding it to your configuration. Type: string Default: "" # Examples: password: foo password: ${KEY_PASSWORD} tls.enable_renegotiation Whether to allow the remote server to repeatedly request renegotiation. Enable this option if you’re seeing the error message local error: tls: no renegotiation. Type: bool Default: false tls.root_cas An optional root certificate authority to use. This is a string, representing a certificate chain from the parent trusted root certificate, to possible intermediate signing certificates, to the host certificate. This field contains sensitive information that usually shouldn’t be added to a configuration directly. For more information, see Manage Secrets before adding it to your configuration. Type: string Default: "" # Examples: root_cas: |- -----BEGIN CERTIFICATE----- ... -----END CERTIFICATE----- tls.root_cas_file An optional path of a root certificate authority file to use. This is a file, often with a .pem extension, containing a certificate chain from the parent trusted root certificate, to possible intermediate signing certificates, to the host certificate. Type: string Default: "" # Examples: root_cas_file: ./root_cas.pem tls.skip_cert_verify Whether to skip server side certificate verification. Type: bool Default: false url The base URL of the schema registry service. Type: string Back to top × Simple online edits For simple changes, such as fixing a typo, you can edit the content directly on GitHub. Edit on GitHub Or, open an issue to let us know about something that you want us to change. Open an issue Contribution guide For extensive content updates, or if you prefer to work locally, read our contribution guide . Was this helpful? thumb_up thumb_down group Ask in the community mail Share your feedback group_add Make a contribution 🎉 Thanks for your feedback! retry schema_registry_encode