Toivo, My initial design was also much simpler, and more like what you described. But Matt made some suggestions towards a bigger picture allowing for a wider audience and more use cases and I've been building off of those guidelines.
I've got a lot more code done than what is checked into Github in my local branch that I have been testing out locally. Mark Payne provided a lot of good feedback a few days ago and I'm planning to put some of that in place over the next couple of days. My original focus was only on QueryDatabaseTable, but about half of the settings that apply to QueryDatabaseTable also apply to ExecuteSQL. Allowing for a user to select an output format is exactly what I'm going for. What I actually want to do eventually is figure out how to support multiple simultaneous output formats and add dynamic relationships so that I can get both Avro and ORC at once without having to do multiple conversions; but I figured I'd start small :) Thanks, Peter -----Original Message----- From: Toivo Adams [mailto:[email protected]] Sent: Saturday, September 03, 2016 7:53 AM To: [email protected] Subject: Re: ExecuteSql output formats. Hi Matt, I did not notice Peter work, thanks for pointing it out. You are right, controller service approach helps to solve dependency problems. I read “Looking for feedback on my WIP Design” and code and this looks much bigger than my simple solution. I have to think about it. Thanks Toivo -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/ExecuteSql-output-formats-tp13265p13270.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
