[
https://issues.apache.org/jira/browse/NIFI-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241249#comment-15241249
]
Dave Torok commented on NIFI-1772:
----------------------------------
Certainly this small feature would be subsumed in the Configuration Management
solution proposal.
https://cwiki.apache.org/confluence/display/NIFI/Configuration+Management+of+Flows
At a minimum you want automatic state change recording / versioning (for free
you get "unlimited undo" as part of rollback). "tagging" a state (the
equivalent of pressing the "back up flow" button) giving you timestamped and/or
named versions / known good versions.
Of course the temptation is to start doing everything a VCS does with diffs,
merges, branches, releases, etc. at which point either (a) pluggable
integration with known VCS starts to look better or (b) Use an internal 'git'
as both the flow/template directory structure as well as the commit mechanism?
> Back-up Flow does not create backup on NCM Cluster Manager
> ----------------------------------------------------------
>
> Key: NIFI-1772
> URL: https://issues.apache.org/jira/browse/NIFI-1772
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 0.5.1
> Reporter: Dave Torok
> Priority: Minor
>
> When in clustered mode, Using the "back-up flow" action creates back-ups on
> each of the nodes but not on the Cluster Manager. The expectation is that an
> archive/backup is created on the Cluster Manager as well, particularly
> because that where the 'master' flow is kept for all the worker nodes.
> The documentation of the feature describes the difference between "flow.tar"
> and "flow.xml.gz" but does not state that backups are only created on the
> nodes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
