You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Peter Wicks (JIRA)" <ji...@apache.org> on 2018/06/29 18:59:00 UTC
[jira] [Commented] (NIFI-4517) Create a processor to allow SQL
results to be output as records in any supported format
(ExecuteSQLToRecord)
[ https://issues.apache.org/jira/browse/NIFI-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16528098#comment-16528098 ]
Peter Wicks commented on NIFI-4517:
-----------------------------------
[~mattyb149], does this need to be a new processor? Could we just add an optional RecordWriter property to ExecuteSQL, that if not set defaults to using the existing Avro?
> 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)