You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (Jira)" <ji...@apache.org> on 2019/10/24 15:44:00 UTC
[jira] [Updated] (NIFI-6805) When ControllerServiceNode is logged,
it no longer includes the UUID of the Controller Service
[ https://issues.apache.org/jira/browse/NIFI-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Payne updated NIFI-6805:
-----------------------------
Fix Version/s: 1.11.0
Status: Patch Available (was: Open)
> 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)