[
https://issues.apache.org/jira/browse/NIFI-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Wicks updated NIFI-4517:
------------------------------
Description:
ExecuteSQL and QueryDatabaseTable 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.
ExecuteSQL and QueryDatabaseTable processors should be updated with a
RecordSetWriter implementation. 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.
was:
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.
> Allow SQL results to be output as records in any supported format
> -----------------------------------------------------------------
>
> Key: NIFI-4517
> URL: https://issues.apache.org/jira/browse/NIFI-4517
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Peter Wicks
> Priority: Major
>
> ExecuteSQL and QueryDatabaseTable 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.
> ExecuteSQL and QueryDatabaseTable processors should be updated with a
> RecordSetWriter implementation. 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)
