I'm working on a change to QueryDatabaseTable (and eventually would apply to 
ExecuteSQL) to allow users to choose the output format, so something besides 
just Avro.  I'm planning to put in a ticket soon for my work.

Goals:

-          If this update goes out no user should be affected, as defaults will 
work the way they have before.

-          Don't want to muck up dependencies of standard processors with lots 
of other libraries to support multiple formats. As such I have implemented it 
using Controller Services to make the converters pluggable.

-          Would like to support these output formats to start:

o   Avro (This one is already in my commit, as I copy/pasted the code over; but 
the logic has now been moved to an appropriate library, which I like)

o   ORC (Would be implemented in the HIVE library)

o   JSON (No idea where I would put this processor, unless it's in a new module)

o   Delimited (No idea where I would put this processor, unless it's in a new 
module)

Here is my commit: 
https://github.com/patricker/nifi/commit/01a79804f60b6be0f86499949712cd9118fb4f7f

I'd appreciate feedback on design/implementation.  I have the guts in there of 
how I was planning to implement this.

Thanks,
  Peter

Reply via email to