Yes it would be a ControllerService as you described. There is currently three implementation : * AvroSchemaRegistry * ConfluentSchemaRegistry * HortonworksSchemaRegistry
It could be based on something like them. May be I should send something on Jira or somewhere else to submit the idea to NiFi developers ? But it also means that the processor JoltTransformJSON and JoltTransformRecord should be changed. Le mer. 20 nov. 2019 à 16:08, Joe Witt <joe.w...@gmail.com> a écrit : > Hello > > Is the idea to have a place to store Jolt specifications that you could > then access in various components? > > If so a simple ControllerService such as 'JoltSpecControllerService' which > has a list of keys (names of specs) and values (the spec) would probably do > the trick. > > Thanks > > On Wed, Nov 20, 2019 at 10:04 AM Otto Fowler <ottobackwa...@gmail.com> > wrote: > >> I think that is a great idea, I’d suggest the same thing for protobuf >> specs as well. >> >> Even if the first step is the registry supporting raw bytes access and >> support…. >> >> >> >> >> On November 20, 2019 at 09:28:23, Etienne Jouvin (lapinoujou...@gmail.com) >> wrote: >> >> Hello all. >> >> >> For reader and writers, there is the possibility to store the schema >> inside a schema registry. >> What do you think about having this type of mechanism for >> JolftTransformation ? >> Currently, I can put Jolt specification in variables and get them from >> it, but I think it could be nice tohave same as schema registry. >> >> Regards. >> >> Etienne Jouvin >> >> >>
