[
https://issues.apache.org/jira/browse/NIFI-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011157#comment-16011157
]
ASF subversion and git services commented on NIFI-3763:
-------------------------------------------------------
Commit bf15502e1994c68d706a2a2749495b57fd9a11e4 in nifi's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=bf15502 ]
NIFI-3763 Add new processor to log user defined messages built with NiFi
Expression Language
Signed-off-by: Matt Burgess <[email protected]>
This closes #1737
> Add new processor to log user defined messages built with NiFi Expression
> Language
> ----------------------------------------------------------------------------------
>
> Key: NIFI-3763
> URL: https://issues.apache.org/jira/browse/NIFI-3763
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Reporter: Peter Horvath
> Priority: Minor
>
> Sometimes it would be very useful to have a NiFi processor, which can simply
> log messages as defined by the DataFlow Manager (DFM/operator).
> Such functionality would be a powerful aid for _debugging_ running NiFi
> dataflows. The DFM should be able to specify the single line log message
> using NiFi Expression Language. Similarly to the existing LogAttribute
> processor, the DataFlow Manager should be able to specify the log level
> (trace, debug, info, warn, error) at which the log line is written.
> While the functionality can be achieved by combining UpdateAttribute and
> LogAttribute processor nodes, having to use three separate nodes (adding the
> log message as an attribute, logging the attribute, then removing the
> attribute from the flowfile's processing context) and a temporary attribute
> to convey the message is overly complex and clutters the flow diagram.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
