[
https://issues.apache.org/jira/browse/NIFI-15061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18027892#comment-18027892
]
ASF subversion and git services commented on NIFI-15061:
--------------------------------------------------------
Commit e81448f98a50ba1f79f83596563668e7a29b330d in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e81448f98a ]
NIFI-15061 Fixed Logging Context initialization for Controller Services
- Added default constructor for StandardLoggingContext for explicit null
Grouped Component references
- Added non-null requirement to StandardLoggingContext constructor to avoid
unexpected initialization
Signed-off-by: Pierre Villard <[email protected]>
This closes #10394.
> Incorrect Logging Context for Controller Services
> -------------------------------------------------
>
> Key: NIFI-15061
> URL: https://issues.apache.org/jira/browse/NIFI-15061
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 2.6.0
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The StandardLoggingContext provides Process Group attributes for the standard
> implementation of the ComponentLog interface. The current implementation
> takes a single argument in the constructor, which can be null, requiring
> later initialization using the setComponent method. Based on current
> behavior, the StandardLoggingContext for Controller Services is never
> initialized using the setComponent method because the ExtensionBuilder
> creates two different instances of the StandardLoggingContext. Logging
> Context creation for Controller Services should be corrected, and references
> to the StandardLoggingContext should be reviewed and updated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
