[ https://issues.apache.org/jira/browse/NIFIREG-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676159#comment-16676159 ]
ASF GitHub Bot commented on NIFIREG-205: ---------------------------------------- GitHub user ijokarumawak opened a pull request: https://github.com/apache/nifi-registry/pull/146 NIFIREG-205: Allow Git repo to delete a flow with snapshot version 0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijokarumawak/nifi-registry nifireg-205 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-registry/pull/146.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 #146 ---- commit e225f8db39c85467bb95271b495887b6cceba2d6 Author: Koji Kawamura <ijokarumawak@...> Date: 2018-11-06T05:24:08Z NIFIREG-205: Allow Git repo to delete a flow with snapshot version 0 ---- > NiFi Registry DB gets out of sync with git repository, no apprent remediation > ----------------------------------------------------------------------------- > > Key: NIFIREG-205 > URL: https://issues.apache.org/jira/browse/NIFIREG-205 > Project: NiFi Registry > Issue Type: Bug > Environment: Centos 7.5 > Reporter: Dye357 > Assignee: Koji Kawamura > Priority: Major > > I've observed a couple issues with the GitFlowPersistenceAdapter: > # When adding a new process group to NIFREG If for any reason the git > repository is in a "dirty" (untracked file) state the adding of the process > group fails. However an entry is still created in the DB with a version of 0. > Once in this state you cannot delete the flow from NIFIREG and you cannot > restart version control from nifi with the same name. I assume the only way > to fix this is to manually go into the DB and delete the record. > # When using Remote To Push, if the push fails the same behavior in #1 is > exhibited. It's not reasonable to expect that a push will always succeed. The > remote git repository could be offline for maintenance etc... > Steps to reproduce: > # Start nifi registry with an empty db and clean git repo. > # add an untracked file to the git repo but do-not commit it. > # Start a processgroup under version control. > # Expect Failure in Nifi UI > # Expect Exception in Log saying untracked files in git repo. > # Delete flow from nifi-registry using Actions -> Delete. > # Expect Failure case, recieve error deleting flow message. > # Refresh nifi-registry UI - flow is still present, version is 0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)