Provides a Schema Registry that interacts with the Confluent Schema Registry so that those Schemas that are stored in the Confluent Schema Registry can be used in NiFi. The Confluent Schema Registry has a notion of a "subject" for schemas, which is their terminology for a schema name. When a Schema is looked up by name by this registry, it will find a Schema in the Confluent Schema Registry with that subject.


schema, registry, confluent, avro, kafka


In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.

Display NameAPI NameDefault ValueAllowable ValuesDescription
Schema Registry URLsurlhttp://localhost:8081A comma-separated list of URLs of the Schema Registry to interact with
Supports Expression Language: true (will be evaluated using variable registry only)
SSL Context Servicessl-contextController Service API:
Implementations: StandardRestrictedSSLContextService
Specifies the SSL Context Service to use for interacting with the Confluent Schema Registry
Communications Timeouttimeout30 secsSpecifies how long to wait to receive data from the Schema Registry before considering the communications a failure
Cache Sizecache-size1000Specifies how many Schemas should be cached from the Schema Registry
Cache Expirationcache-expiration1 hourSpecifies how long a Schema that is cached should remain in the cache. Once this time period elapses, a cached version of a schema will no longer be used, and the service will have to communicate with the Schema Registry again in order to obtain the schema.
Authentication Typeauthentication-typeNONE
  • NONE
HTTP Client Authentication Type for Confluent Schema Registry
UsernameusernameUsername for authentication to Confluent Schema Registry

This Property is only considered if the [Authentication Type] Property has a value of "BASIC".
PasswordpasswordPassword for authentication to Confluent Schema Registry
Sensitive Property: true

This Property is only considered if the [Authentication Type] Property has a value of "BASIC".

Dynamic Properties:

Supports Sensitive Dynamic Properties: No

Dynamic Properties allow the user to specify both the name and value of a property.

request.header.*String literal, may not be emptyProperties that begin with 'request.header.' are populated into a map and passed as http headers in REST requests to the Confluent Schema Registry
Supports Expression Language: false

State management:

This component does not store state.


This component is not restricted.

System Resource Considerations:

None specified.