[
https://issues.apache.org/jira/browse/NIFI-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16691268#comment-16691268
]
ASF subversion and git services commented on NIFI-5828:
-------------------------------------------------------
Commit 54402a1ecda4b11ca10472fada9adce484b031c1 in nifi's branch
refs/heads/master from [~colindean]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=54402a1 ]
NIFI-5828: Documents behavior of ExecuteSQL attrs when Max Rows Per Flow File
is enabled
This closes #3177.
Signed-off-by: Koji Kawamura <[email protected]>
> 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)
