[
https://issues.apache.org/jira/browse/NIFI-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745516#comment-15745516
]
ASF GitHub Bot commented on NIFI-3192:
--------------------------------------
GitHub user JPercivall opened a pull request:
https://github.com/apache/nifi/pull/1325
NIFI-3192 Adding a check if the FlowFile is null to UpdateAttribute
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/JPercivall/nifi NIFI-3192
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1325.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 #1325
----
commit c45b292a1a3975346d66a6e01fe1183402bcbc0e
Author: jpercivall <[email protected]>
Date: 2016-12-13T16:10:25Z
NIFI-3192 Adding a check if the FlowFile is null to UpdateAttribute
----
> 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)
