[
https://issues.apache.org/jira/browse/NIFI-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16691241#comment-16691241
]
Colin Dean commented on NIFI-5828:
----------------------------------
Thanks, [~ijokarumawak].
bq. I agree, clarifying doc on those attribute would be helpful.
https://github.com/apache/nifi/pull/3177
bq. Also, we could add another attribute representing the number of rows in the
result set such as "executesql.row.count.total".
Split off as NIFI-5831. String changes are quick but I'm out for the next week
for the US Thanksgiving holiday… I'll take a look at that when I return.
> ExecuteSQL executesql.row.count meaning changes when Max Rows Per Flow File > > 0
> -------------------------------------------------------------------------------
>
> Key: NIFI-5828
> URL: https://issues.apache.org/jira/browse/NIFI-5828
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.8.0
> Environment: Linux, MSSQL 2016
> Reporter: Colin Dean
> Priority: Major
> Labels: regression
>
> When *Max Rows Per Flow File* ({{esql-max-rows}}) is set greater than 0 to
> enable it, the {{executesql.row.count}} attribute on the resulting FlowFiles
> is not the number of rows in the result set but rather the number of rows in
> the FlowFile.
> This is a deviation from documented behavior, which is "Contains the number
> of rows returned in the select query".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
