You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Koji Kawamura (JIRA)" <ji...@apache.org> on 2018/11/19 05:20:00 UTC
[jira] [Assigned] (NIFI-5828) ExecuteSQL executesql.row.count
meaning changes when Max Rows Per Flow File > 0
[ https://issues.apache.org/jira/browse/NIFI-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koji Kawamura reassigned NIFI-5828:
-----------------------------------
Assignee: Colin Dean
> 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: 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)