I would like to have a discussion around the archetypes. Right now Nifi
has two archetypes : A controller service and a processor. Both are
simple, and don’t reference anything outside of them.
I have a few topics for comment here:
1. Are there things about the current archetypes that could be improved or
refactored such that processors produced need less modification when
submitted?
example: The processor archetype’s method of initializing it’s properties
vs. how standard processors do it, or in fact the archetype service does it
2. Are there common patterns of use that should be represented in the
current archetypes?
- verification / use of built in verifications
- service usage
3. Are there patterns of use or components that should have an archetype
that don’t have one?
- reporting
- record readers/writers
- processors that work with records
- new bundle patterns such as the Processor -> API Service pattern, so an
archetype with a processor and service that work together?
4. ?????
I would like to gather feedback to create some jiras around this.
Thanks!
ottO
