Hi guys, I am thinking to increase the footprint of NiFi in my org to extend it to less technical roles. I have a few questions:
1) is there any plans to support easy dependencies at some point? We are aware of all the current options (wait-notify, kafka, mergerecord/mergecontent etc.) and all of them are still hard and not reliable. For non-technical roles, we really need very stupid simple way to define classical dependencies like run task C only after task A and B are finished. I realize it is a challenge because of the whole concept of NiFi with flowfiles (which we do love being on a technical side of the house), but I really do not want to get another ETL/scheduling tool. 2) is it fairly easy to build and support our custom version of NiFi-light, when we remove all the processors that we do not want to expose to non-technical people? The idea is to remove all the processors that consume cpu/ram to force them benefit from our Big Data systems and not use NiFi to do the actual processing. We would like to leave these capabilities to our data engineering team while shift our analysts to ELT/ELTL paradigm to let them run SQL and benefit from Big Data engines. 3) what would be recommended set up for multiple decentralized teams? separate NiFi instances when they can support their own jobs while our admin supports all these instances? or one large NiFi cluster when everyone works on the same NiFi cluster? We do not want them to step on each other jobs, see each other failure alerts/bulletins etc. We want to make it look like their team's own environment. Not sure if NiFi policies are mature enough to provide this sort of isolation. Thanks, Boris
