[
https://issues.apache.org/jira/browse/NIFI-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15510258#comment-15510258
]
ASF subversion and git services commented on NIFI-2749:
-------------------------------------------------------
Commit 938c7cccb8b251d4a1390cf0078b14f53bc94a57 in nifi's branch
refs/heads/master from [~patricker]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=938c7cc ]
NIFI-2749
Signed-off-by: Matt Burgess <mattyb...@apache.org>
This closes #997
> 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
> Fix For: 1.1.0
>
>
> 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)
