[ 
https://issues.apache.org/jira/browse/NIFIREG-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763593#comment-16763593
 ] 

Mark Payne commented on NIFIREG-224:
------------------------------------

[~chad.woodhead] is your intent here to show this in NiFi? I.e., when the user 
chooses to see changes between the current version of their flow and the 
"versioned version" of their flow? If so, we should probably move this Jira to 
the NIFI Jira instead of the NIFIREG Jira.

It is a reasonable ask and makes a lot of sense. Unfortunately, it's very 
nontrivial to do at this time. NiFi is not tracking the individual changes to 
the Process Group. Instead, when you ask to see Local Changes, it reaches out 
to the Registry to pull the flow, and then performs a 'diff' of the local flow 
and the versioned flow. Each change that is made in NiFi *is* tracked in the 
audit log (Go to the hamburger menu in top right and go to History) but this is 
not currently tracked at the Process Group level, only the flow level. I can 
definitely see how that would make sense, though, as a future improvement - 
just wanted to give a heads up that this isn't something as simple as just 
showing a couple of extra fields in the UI :)

> On NiFi UI, show the user and timestamp when viewing local changes on a 
> versioned PG
> ------------------------------------------------------------------------------------
>
>                 Key: NIFIREG-224
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-224
>             Project: NiFi Registry
>          Issue Type: New Feature
>    Affects Versions: 0.4.0
>            Reporter: Chad Woodhead
>            Priority: Minor
>              Labels: features
>
> On the NiFi UI, it would be very helpful to show the user and timestamp when 
> viewing local changes on a versioned PG. When multiple developers are working 
> on the same flows/PGs, it would be very helpful to see who made local changes 
> and what time those changes were made.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to