[
https://issues.apache.org/jira/browse/NIFI-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745559#comment-15745559
]
ASF GitHub Bot commented on NIFI-3192:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/1325
+1 LGTM, functionally tested with and without (using a high-volume flow
through UpdateAttribute with 3 concurrent tasks), verified this fixes the
issue. Thank you! Merging to master
> UpdateAttribute needs to check if FlowFile is null
> --------------------------------------------------
>
> Key: NIFI-3192
> URL: https://issues.apache.org/jira/browse/NIFI-3192
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Joseph Percivall
> Assignee: Joseph Percivall
>
> With NIFI-1582 UpdateAttribute was changed to properly take one flowfile at a
> time and expose the throughput configuration options in the UI but a check to
> see if the incoming FlowFile was null was left out. In the event a penalized
> flowfile is sent to the processor it will log errors and yield the processor
> until it able to pull a flowfile off the queue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
