org.apache.nifinifi-confluent-platform-nar2.0.0org.apache.nifinifi-standard-shared-nar2.0.02.0.0HEADUNKNOWN2f13b60org.apache.nifi.confluent.schemaregistry.ConfluentEncodedSchemaReferenceReaderCONTROLLER_SERVICEReads Schema Identifier according to Confluent encoding as a header consisting of a byte marker and an integer represented as four bytesconfluentschemaregistrykafkaavroorg.apache.nifi.schemaregistry.services.SchemaReferenceReaderorg.apache.nifinifi-standard-services-api-nar2.0.0org.apache.nifi.confluent.schemaregistry.ConfluentEncodedSchemaReferenceWriterCONTROLLER_SERVICEWrites Schema Identifier according to Confluent encoding as a header consisting of a byte marker and an integer represented as four bytesconfluentschemaregistrykafkaavroorg.apache.nifi.schemaregistry.services.SchemaReferenceWriterorg.apache.nifinifi-standard-services-api-nar2.0.0org.apache.nifi.confluent.schemaregistry.ConfluentSchemaRegistryCONTROLLER_SERVICEProvides 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.schemaregistryconfluentavrokafkaurlSchema Registry URLsA comma-separated list of URLs of the Schema Registry to interact withhttp://localhost:8081truefalsetrueENVIRONMENTfalsefalsessl-contextSSL Context ServiceSpecifies the SSL Context Service to use for interacting with the Confluent Schema Registryorg.apache.nifi.ssl.SSLContextServiceorg.apache.nifinifi-standard-services-api-nar2.0.0falsefalsefalseNONEfalsefalsetimeoutCommunications TimeoutSpecifies how long to wait to receive data from the Schema Registry before considering the communications a failure30 secstruefalsefalseNONEfalsefalsecache-sizeCache SizeSpecifies how many Schemas should be cached from the Schema Registry1000truefalsefalseNONEfalsefalsecache-expirationCache ExpirationSpecifies 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.1 hourtruefalsefalseNONEfalsefalseauthentication-typeAuthentication TypeHTTP Client Authentication Type for Confluent Schema RegistryNONEBASICBASICNONENONEfalsefalsefalseNONEfalsefalseusernameUsernameUsername for authentication to Confluent Schema RegistryfalsefalsefalseNONEfalsefalseauthentication-typeAuthentication TypeBASICpasswordPasswordPassword for authentication to Confluent Schema RegistryfalsetruefalseNONEfalsefalseauthentication-typeAuthentication TypeBASICrequest.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 RegistryNONEorg.apache.nifi.schemaregistry.services.SchemaRegistryorg.apache.nifinifi-standard-services-api-nar2.0.0