[
https://issues.apache.org/jira/browse/NIFI-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434514#comment-16434514
]
ASF subversion and git services commented on NIFI-4997:
-------------------------------------------------------
Commit b7272e3f3282c6e42eb7ada86d15f32188527ccf in nifi's branch
refs/heads/master from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=b7272e3 ]
NIFI-4997:
- Fixing process group audit advice.
- Setting spring security user in background threads.
- Removing unnecessary overloaded methods.
This closes #2626.
Signed-off-by: Mark Payne <marka...@hotmail.com>
> Actions taken on process groups do not appear in flow configuration history
> ---------------------------------------------------------------------------
>
> Key: NIFI-4997
> URL: https://issues.apache.org/jira/browse/NIFI-4997
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 1.4.0
> Environment: CentOS 7, Docker
> Reporter: Craig Becker
> Assignee: Matt Gilman
> Priority: Major
>
> Selecting a process group and executing a stop or start action does not cause
> anything to be logged in the flow configuration history. The current behavior
> makes it impossible to trace who/when a process group was turned off.
>
> The expected/desired behavior would be to either add a log entry per
> processor that was stopped/started, or to log that the process group was
> stopped/started.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
