Description:
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.
Tags:
schema, registry, confluent, avro, kafka
Properties:
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.
Name |
Default Value |
Allowable Values |
Description |
Schema Registry URLs |
http://localhost:8081 |
A comma-separated list of URLs of the Schema Registry to interact with Supports Expression Language: true |
|
SSL Context Service |
Controller Service API: SSLContextService Implementations: StandardSSLContextService StandardRestrictedSSLContextService |
Specifies the SSL Context Service to use for interacting with the Confluent Schema Registry | |
Communications Timeout |
30 secs | Specifies how long to wait to receive data from the Schema Registry before considering the communications a failure | |
Cache Size |
1000 | Specifies how many Schemas should be cached from the Schema Registry | |
Cache Expiration |
1 hour | Specifies how long a Schema that is cached should remain in the cache. Once this time elapses, a cached version of a schema will no longer be used, and the service will have to communicate with the Schema Registry again to obtain the schema. |
State management:
This component does not store state.
Restricted:
This component is not restricted.