You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pere Urbon-Bayes (JIRA)" <ji...@apache.org> on 2017/03/05 06:35:32 UTC
[jira] [Commented] (NIFI-3533) Enhance QueryDatabaseTable processor
to output different formats
[ https://issues.apache.org/jira/browse/NIFI-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896088#comment-15896088 ]
Pere Urbon-Bayes commented on NIFI-3533:
----------------------------------------
I agree with this, however I am wondering if there are benefits of having avro by default? from the user point of view, I agree with you, generally my workflow use to be read -> process json -> store.
In my opinion having such an option will reduce the workflow, mostly redundant complexity.
> Enhance QueryDatabaseTable processor to output different formats
> ----------------------------------------------------------------
>
> Key: NIFI-3533
> URL: https://issues.apache.org/jira/browse/NIFI-3533
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.1.1
> Reporter: Uwe Geercken
> Priority: Minor
> Labels: database, format, query
>
> The QueryDatabaseTable processor outputs in AVRO format.
> Enhance the processor to allow the user to select the desired output format. Such as JSON, CSV, etc.
> This can be achieved using other processors, but converting to AVRO and then to e.g. CSV it double work and slows down the process.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)