[
https://issues.apache.org/jira/browse/NIFI-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15475815#comment-15475815
]
ASF GitHub Bot commented on NIFI-2749:
--------------------------------------
GitHub user patricker opened a pull request:
https://github.com/apache/nifi/pull/997
NIFI-2749
Bug fix for NIFI-2641, includes unit test.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/patricker/nifi NIFI-2749
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/997.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #997
----
commit dda8ea390418cdd465e38beb32c4086fa9fbbb4c
Author: Peter Wicks <[email protected]>
Date: 2016-09-09T03:37:21Z
NIFI-2749
----
> 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)
