Toivo - this thread seems important and does not appear to have come to a resolution. Do you want to pick this back up or are you comfortable with where it is as for now?
On Wed, Dec 2, 2015 at 12:39 PM, dcave <[email protected]> wrote: > Adding multiple input and output format support would complicate the > usability and ongoing maintenance of the SQL/NoSQL processors. > Additionally, as you suggested it is impossible to select a "correct" format > or set of formats that can handle all potential needs. > > A simpler and more streamlined solution is to put the emphasis on having > Convert processors available that can handle specific cases as they come up > as your last comment suggested. This also keeps processor focus on one > specific task rather than having Get/Put/Convert hybrids that can lead to > unneeded complexity and code bloat. > > This is in line with Benjamin's line of work. > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/Common-data-exchange-formats-and-tabular-data-tp3508p5551.html > Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
