mosermw commented on PR #9967:
URL: https://github.com/apache/nifi/pull/9967#issuecomment-3005502421

   Thanks for having a look at this PR @NissimShiman
   
   > I've noticed that the list of local changes has a "Go To" option next to 
the "Component Bundle Changed" which doesn't lead anywhere. Would it be a big 
deal to remove that option for this?
   
   I was able to get something to work, then I noticed there is an [open PR for 
NIFI-14637](https://github.com/apache/nifi/pull/10028) that does almost exactly 
what I was going to do.  So I think we can wait for that PR to merge, then I 
can modify this PR to rebase and take advantage of that code.
   
   > Also noticed that if a versioned PG is in flow, NiFi is restarted, PG is 
updated (and new version pushed to registry) and then is rolled back and then a 
new change is made (but not committed yet) , the component bundle update does 
not show up as a local change, but if NiFi is again restarted it will. Is this 
expected?
   
   Yes it's expected.  This is because the ProcessGroup stores a copy of its 
versioned snapshot, which typically has already been modified from what's in 
the FlowRegistry.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to