Igor, The term ETL has a lot of baggage associated with it. What NiFi was built to do is dataflow management. There are already a lot of tools out there that address the typical relational database ETL space and NiFi doesn't need to replicate all of those functions. So probably best to just focus on use cases/problems and see if NiFi handles them nicely now, doesn't handle them nicely now but should be made to do so, or doesn't handle them nicely and it should always be left to some other system.
Thanks Joe On Wed, Dec 16, 2015 at 7:10 PM, Igor Kravzov <igork.ine...@gmail.com> wrote: > The question is "Is NiFi supposed to be a full ETL tool"? > On Dec 16, 2015 11: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. >> > >>
