You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Colin Dean (JIRA)" <ji...@apache.org> on 2018/11/16 18:07:00 UTC

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

Colin Dean created NIFI-5828:
--------------------------------

             Summary: 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


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)