[
https://issues.apache.org/jira/browse/NIFI-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994613#comment-15994613
]
ASF GitHub Bot commented on NIFI-3763:
--------------------------------------
GitHub user peter-gergely-horvath opened a pull request:
https://github.com/apache/nifi/pull/1737
NIFI-3763 Add new processor to log user defined messages built with N…
This pull request adds support described in [NIFI-3763: Add new processor
to log user defined messages built with NiFi Expression
Language](https://issues.apache.org/jira/browse/NIFI-3763)
Notes:
- Contribution check Maven build (`mvn -Pcontrib-check clean install`)
completed **SUCCESSFULLY**
- The request has been rebased aginst NiFi master
- This pull request does **NOT** bring new dependencies
- Properties added to the processor have their appropriate display name
"_Log Level_", "_Log prefix_" and "_Log message_"
- This change is accompanied by a unit test, see
`org.apache.nifi.processors.standard.TestLogString `
-- BEGIN OF ORIGINAL PULL MESSAGE TEMPLATE --
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [ ] Is your initial contribution a single, squashed commit?
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/peter-gergely-horvath/nifi master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1737.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 #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)
