[
https://issues.apache.org/jira/browse/NIFI-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16959298#comment-16959298
]
ASF subversion and git services commented on NIFI-6805:
-------------------------------------------------------
Commit 8079d2531e561ad5dbbfe9e8dc4b818d694d57a6 in nifi's branch
refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8079d25 ]
NIFI-6805, NIFI-6806: Updated toString() of StandardControllerServiceNode so
that it includes the component's type and UUID, updated the more generic
Exception Mappers to include stack traces regardless of the log level that is
enabled
This closes #3840
Signed-off-by: Mike Thomsen <mthom...@apache.org>
> When ControllerServiceNode is logged, it no longer includes the UUID of the
> Controller Service
> ----------------------------------------------------------------------------------------------
>
> Key: NIFI-6805
> URL: https://issues.apache.org/jira/browse/NIFI-6805
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.10.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The `toString()` method of StandardControllerServiceNode was changed in
> NIFI-6201. The new `toString()` method no longer contains the CS's UUID. This
> means that when log messages are generated about a Controller Service,
> there's no easy way to track it back to the Controller Service that is
> affected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
