Hi, Using an external schema registry is the way to go. The embedded one is meant for ease of use, but once you grow beyond an initial phase, the best practice is to have a full service and potentially use standard InvomeHTTP to perform operations beyond just lookups.
Does it help? Andrew On Mon, Oct 23, 2017, 6:43 AM Sönke Liebau <soenke.lie...@opencore.com> wrote: > Hi everybody, > > I am developing a custom ingest processor that writes data out as a binary > avro stream. Currently I simply store the schema in an attribute of the > flowfile and that works quite nicely with an AvroRecordReader deserializing > it. > > To make things "nicer" I thought I'd have a look at the AvroSchemaRegistry > and use that to store and look up schemas. However I cannot find a way for > my processor to register a schema with the registry, but only to retrieve > schemas [1]. I understand that I can manually add the schema as a dynamic > property, but what I want to accomplish is that the processor can > automatically add evolving schemas to the registry at runtime. > > Am I missing something obvious here, or is the registry simply not > supposed to work like that? > > Kind regards, > Sönke > > [1] > https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-registry-bundle/nifi-registry-service/src/main/java/org/apache/nifi/schemaregistry/services/AvroSchemaRegistry.java#L83 >
