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

Posted to issues@nifi.apache.org by "Matt Burgess (JIRA)" <ji...@apache.org> on 2016/09/09 03:53:20 UTC

[jira] [Updated] (NIFI-2749) maxvalue Attributes Added by QueryDatabaseTable to FlowFiles May be Incorrect

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

Matt Burgess updated NIFI-2749:
-------------------------------
    Status: Patch Available  (was: Open)

> maxvalue Attributes Added by QueryDatabaseTable to FlowFiles May be Incorrect
> -----------------------------------------------------------------------------
>
>                 Key: NIFI-2749
>                 URL: https://issues.apache.org/jira/browse/NIFI-2749
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.0.0
>            Reporter: Peter Wicks
>            Priority: Minor
>
> NIFI-2641 caused maxvalue attributes to be placed onto FlowFiles generated by QueryDatabaseTable.  However if QDB is using MAX_ROWS_PER_FLOW_FILE to split the ResultSet into multiple FlowFiles then the value attached to the FlowFile will just be the maximum seen so far, and not necessarily the final Maximum.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)