[
https://issues.apache.org/jira/browse/NIFI-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557333#comment-14557333
]
Toivo Adams commented on NIFI-626:
----------------------------------
Can we assume query result will not be very big?
Usually not more than tens of thousand rows.
So every onTrigger call will create only one FlowFile.
Of course it's not very difficult to create many FlowFile's instead of one.
But supporting also back pressure in case of many generated FlowFile's can be
tricky.
Should we limit how many rows will be read from database?
Bad select query can easily create huge amount of rows.
Thanks
Toivo
> ExecuteSQL processor for executing arbitrary SQL queries
> --------------------------------------------------------
>
> Key: NIFI-626
> URL: https://issues.apache.org/jira/browse/NIFI-626
> Project: Apache NiFi
> Issue Type: Sub-task
> Reporter: Toivo Adams
> Assignee: Toivo Adams
>
> For example query can be:
> SELECT * FROM orders WHERE orderId = '${order.id}'
> where ${order.id} is FlowFile attribute.
> Result will serialized using Avro.
> Avro gives as possibility to have query Resultset metadata (column name and
> types) included in FlowFile.
> Also Avro should allow streaming.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
