You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/11 12:40:00 UTC
[jira] [Commented] (NIFI-4997) Actions taken on process groups do
not appear in flow configuration history
[ https://issues.apache.org/jira/browse/NIFI-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433854#comment-16433854 ]
ASF GitHub Bot commented on NIFI-4997:
--------------------------------------
GitHub user mcgilman opened a pull request:
https://github.com/apache/nifi/pull/2626
NIFI-4997: Fixing process group audit advice
NIFI-4997:
- Fixing process group audit advice.
- Setting spring security user in background threads.
- Removing unnecessary overloaded methods.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mcgilman/nifi NIFI-4997
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2626.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 #2626
----
commit 226be20d98cd272d3db514f5ed0dab25afec9ba8
Author: Matt Gilman <ma...@...>
Date: 2018-04-10T14:17:49Z
NIFI-4997:
- Fixing process group audit advice.
- Setting spring security user in background threads.
- Removing unnecessary overloaded methods.
----
> 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)