HI Gunjan, In terms of creating and sending data, certainly seems feasible, but might be a bit heavy handed for your testing purposes. Did you have some more specific ideas in mind or a more pointed example of how you would do this? The way I have typically handled this personally for this kind of integration level testing was to use a separate process group in my NiFi that is talking to other processors within the flow or via a Produce/Consume mechanism with related processor pairs (eg PutTCP/ListenTCP). As my testing changed/evolved, the interactive control was very important for me.
This case may get a bit more support once the community starts making some progress toward centralized management/command and control. On Thu, Sep 1, 2016 at 11:19 AM, Gunjan Dave <[email protected]> wrote: > Hello everyone, minifi as i understand has specific use case of small > footprint data collection agent. > Hiwever, today i was trying it out and saw an interesting possibility, > would need NiFi teams opinion on it. > > Can minifi be also modified to work as test harness agent? Like can > currrently processes a smaller part of the complete data flow. So with > certain enhacements as separate project, can it be also made to work as > test harness? I have further thoughts on it to share if you guys concur > with current thought >
