Ate you thinking about some sort of a converter which can be referenced a la controller service?
Andrew On Sat, Sep 3, 2016, 8:31 AM Toivo Adams <[email protected]> wrote: > Hi, > > Currently Avro is supported, but often other formats are needed. > Workaround is to let ExecuteSql create FlowFile in Avro and immediately > after that (using another processor) convert Avro to some other format. > This is a waste of time and resources. > > Maybe it's wise to add pluggable output format converter? > We can define ResultsetConverter interface and add property OutputConverter > to ExecuteSql processor. > Property OutputConverter accept ResultsetConverter implementation class > name. > If property has value ExecuteSql will try to use provided converter > instead > of Avro. > This way everyone can create its own output formats as needed. > > I am ready to implement a such functionality with some simple > ResultsetConverter implementation. > > What do you think? > > Thanks > Toivo > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/ExecuteSql-output-formats-tp13265.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >
