[
https://issues.apache.org/jira/browse/NIFIREG-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771974#comment-16771974
]
Bryan Bende commented on NIFIREG-228:
-------------------------------------
Wondering if this is related to this commit for NIFIREG-205 which isn't
released yet?
[https://github.com/apache/nifi-registry/commit/312a179b6780847fd9986b7b6515622103c2e933]
> Cannot delete a flow with no versioned snapshots
> ------------------------------------------------
>
> Key: NIFIREG-228
> URL: https://issues.apache.org/jira/browse/NIFIREG-228
> Project: NiFi Registry
> Issue Type: Bug
> Reporter: Kevin Doran
> Priority: Minor
>
> I have not verified/reproduced this yet. This bug reported on stack overflow:
> https://stackoverflow.com/questions/54744738/cannot-delete-a-flow-in-nifi-registry-via-http-call-when-using-git-as-storagei
> If saving an initial flow version fails, a flow can be created with no
> versioned flow snapshots. (The flow has {{"versionCount": 0}}). Such a flow
> can be created by saving a flow snapshot that changes the flow name from the
> already versioned flow, according to the reporter on github. The original
> reporter was usingthe git flow persistence provider and the nipyapi
> {{versioning.save_flow_ver()}} call.
> When tying to delete this flow using {{DELETE
> /buckets/<bucketId>/flows/<flowId>}}, it fails with a 409 error.
> The workaround is to save a dummy flow snapshot to get the flow to version 1
> and then the entire flow can be deleted.
> The fix is that such flows (flows without versions) should be deletable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
