[jira] [Commented] (NIFI-4517) Create a processor to allow SQL results to be output as records in any supported format (ExecuteSQLToRecord)

["Ian Neethling (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425243#comment-16425243 ] 

Ian Neethling commented on NIFI-4517:
-------------------------------------

Hi [~mattyb149], do you think this will be a priority for Nifi 1.7.0? I'm not really all that familiar with contributing to Apache projects, but I have developed custom processors before and would be keen to help with this since with the various Schema Registries now available in Nifi a lot of resources could be saved by not including the embedded schema registry in the outputted flowfile, this would of course be configurable.

> Create a processor to allow SQL results to be output as records in any supported format (ExecuteSQLToRecord)
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-4517
>                 URL: https://issues.apache.org/jira/browse/NIFI-4517
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Matt Burgess
>            Priority: Major
>
> ExecuteSQL currently only outputs Avro, and the schema is only available as embedded within the flow file, not as an attribute such as record-aware processors can handle.
> I propose an ExecuteSQLToRecord processor that can be configured with a RecordSetWriter implementation, or to change the existing ExecuteSQL processor (although that might be more invasive and disruptive to existing flows). This will allow output using any writer format (Avro, JSON, CSV, Free-form text, etc.), as well as all the other features therein (such as writing the schema to an attribute, and will avoid the need for a ConvertAvroToXYZ or ConvertRecord processor downstream.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)