[jira] [Updated] (NIFI-5828) ExecuteSQL executesql.row.count meaning changes when Max Rows Per Flow File > 0

["Koji Kawamura (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Koji Kawamura updated NIFI-5828:
--------------------------------
    Priority: Minor  (was: Major)

> 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
>            Assignee: Colin Dean
>            Priority: Minor
>              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)