Mike, Thanks for raising this question, and providing the example repository.
Although it sounds like a POJO-based repository could be useful in some cases, it does not seem like something that should be included for community support. Part of the value of a Schema Registry is a shared location for data description. Although supporting property or file-based Schema Registries is useful in NiFi itself, the general pattern is externalized storage and maintenance of schema definitions. >From another angle, this could be similar to code-first versus contract-first API development. Each approach has its positives and negatives. When it comes to a Schema Registry, however, it seems like the contract needs to be defined outside of code. Introspecting JAR files also raises questions about what to include or exclude, and how to handle edge cases for certain class definitions. This seems like the more significant problem. For this reason, it seems better to rely on external operations to produce Avro schema definitions, rather than supporting that in NiFi itself. Those are my initial thoughts, perhaps others can provide additional perspective. Regards, David Handermann On Sat, Mar 2, 2024 at 9:18 AM Mike Thomsen <mikerthom...@gmail.com> wrote: > > I've had this project on the back burner for a while and wanted to share it > with the team. It's a schema repository implementation that is designed to > take a JAR file with POJOs and use Jackson's schema generation API to > generate Avro schemas from those on startup. It also uses (via Jackson) > Avro annotations to help specify particular implementation details where > necessary. The code can be found here. Haven't worked on it lately, but it > should easily run on 1.25: > > https://github.com/MikeThomsen/nifi-pojo-schema-repository-bundle > > I am planning to get the repo ready for a PR unless someone raises reasons > why including it might be a poor fit. I think for a lot of teams this might > be a killer feature because it would allow them to use Avro with existing > enterprise POJOs and stuff like that without having to write them by hand. > > Thoughts?
