You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Fredrik Sko (JIRA)" <ji...@apache.org> on 2018/06/29 15:41:00 UTC
[jira] [Updated] (NIFIREG-182) Add a way to move on from reverted
versions
[ https://issues.apache.org/jira/browse/NIFIREG-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fredrik Sko updated NIFIREG-182:
--------------------------------
Description:
Quote from {{nifi-users thread "Registry - deleting versions of flow}}".
{quote}I'm not sure if my workflow needs to change using NiFi + NiFi Registry, or if this is a bug or corner-case.
I do the following:
1) Create a new process group, make the initial flow and start version control (ver 1)
2) Modify the workflow and commit (ver 2)
3) Realize the most recent change was defective, and reverts (back to ver 1)
4) Make some new changes
I'm now stuck with NiFi telling me "Local changes have been made and a newer version of the flow is available".
There are two options as I see it:
1) The need for the ability to delete version 2, enabling me to commit my local changes.
2) The ability to commit a new version 3, which is a child of version 1.
As of now (running NiFI 1.7 and Registry 0.2), my only options are to either revert my local changes or stop version control. My current workaround is unfortunately to stop version control, delete the entire flow using the Registry UI and start over again.
Thoughts?
{quote}
Creating Jira ticket as suggested by [~bende] to track development/ideas/thoughts.
was:
Quote from {{nifi-users }}thread {{Registry - deleting versions of flow}}.
{quote}I'm not sure if my workflow needs to change using NiFi + NiFi Registry, or if this is a bug or corner-case.
I do the following:
1) Create a new process group, make the initial flow and start version control (ver 1)
2) Modify the workflow and commit (ver 2)
3) Realize the most recent change was defective, and reverts (back to ver 1)
4) Make some new changes
I'm now stuck with NiFi telling me "Local changes have been made and a newer version of the flow is available".
There are two options as I see it:
1) The need for the ability to delete version 2, enabling me to commit my local changes.
2) The ability to commit a new version 3, which is a child of version 1.
As of now (running NiFI 1.7 and Registry 0.2), my only options are to either revert my local changes or stop version control. My current workaround is unfortunately to stop version control, delete the entire flow using the Registry UI and start over again.
Thoughts?{quote}
Creating Jira ticket as suggested by [~bende] to track development/ideas/thoughts.
> Add a way to move on from reverted versions
> -------------------------------------------
>
> Key: NIFIREG-182
> URL: https://issues.apache.org/jira/browse/NIFIREG-182
> Project: NiFi Registry
> Issue Type: New Feature
> Affects Versions: 0.2.0
> Environment: NiFi 1.7.0, NiFi Registry 0.2.0
> Reporter: Fredrik Sko
> Priority: Minor
>
> Quote from {{nifi-users thread "Registry - deleting versions of flow}}".
> {quote}I'm not sure if my workflow needs to change using NiFi + NiFi Registry, or if this is a bug or corner-case.
>
> I do the following:
> 1) Create a new process group, make the initial flow and start version control (ver 1)
> 2) Modify the workflow and commit (ver 2)
> 3) Realize the most recent change was defective, and reverts (back to ver 1)
> 4) Make some new changes
>
> I'm now stuck with NiFi telling me "Local changes have been made and a newer version of the flow is available".
>
> There are two options as I see it:
>
> 1) The need for the ability to delete version 2, enabling me to commit my local changes.
> 2) The ability to commit a new version 3, which is a child of version 1.
>
> As of now (running NiFI 1.7 and Registry 0.2), my only options are to either revert my local changes or stop version control. My current workaround is unfortunately to stop version control, delete the entire flow using the Registry UI and start over again.
> Thoughts?
> {quote}
>
> Creating Jira ticket as suggested by [~bende] to track development/ideas/thoughts.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)