It is a fair criticism that sometimes the cohesion level of processors can be simply too much. Early on I used to 'fight' to find the right abstraction and argue that others do the same. But what I've found is that it is better to let it happen naturally and to offer options. Matt, I think your approach of giving yourself an option to break into scripting in the middle of the flow in a way that lets you mangle data as needed but benefitting from the strength of the framework is perfect. Matt Burgess is working on NIFI-210 to incorporate those languages and many others.
Thanks Joe On Wed, Dec 16, 2015 at 8:27 AM, Angry Duck Studio <angryduckstu...@gmail.com> wrote: > Shweta, > > I think your issue demonstrates one of my minor complaints with NiFi -- > that you always have to think in terms of several little, built-in pieces > to get a simple job done. Sometimes it's fun, like a puzzle, but other > times, I don't feel like dealing with it. That's why I wrote this: > https://github.com/mring33621/scripting-for-nifi. A short, custom JS or > Groovy script could have handled your JSON data munging in a single stroke. > > -Matt > > On Tue, Dec 15, 2015 at 8:40 PM, shweta <shweta.agg1...@gmail.com> wrote: > >> Thanks Bryan!! Infact I followed the exact approach that you told. Just >> that >> I was clueless about using Mergecontent processor. So I wrote my custom >> script to combine the different outputs and executed it using Execute >> Stream >> command. >> Will try the same with Mergecontent. >> >> >> >> -- >> View this message in context: >> http://apache-nifi-developer-list.39713.n7.nabble.com/How-to-iterate-through-complex-JSON-objects-tp5776p5806.html >> Sent from the Apache NiFi Developer List mailing list archive at >> Nabble.com. >>
