[
https://issues.apache.org/jira/browse/NIFIREG-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671267#comment-16671267
]
ASF GitHub Bot commented on NIFIREG-209:
----------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi-registry/pull/144
@bbende This is really cool! I was able to:
1. Setup two NiFi Registry environment using the same remote Git
repository, but different branches, dev and prod.
2. Create new flow versions at dev and push it to remote origin/dev branch
3. Merge commits to origin/prod branch. Then remove database dir at prod
environment to generate it from updated Git commits.
4. After restarting the prod NiFi Registry, I can import the new flows from
dev to prod environment.
5. Updating existing flow scenario also worked. Even if I restored database
from Git commits, NiFi was able to keep notice new version and change the
deployed PG to a new version.
Haven't looked at the detail of implementation, but from functional point
of view, I'm a huge +1! Great job!
> Support rebuilding metadata DB from Git repo
> --------------------------------------------
>
> Key: NIFIREG-209
> URL: https://issues.apache.org/jira/browse/NIFIREG-209
> Project: NiFi Registry
> Issue Type: Improvement
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
>
> Since the release of git persistence for flow storage, many users have asked
> if there is a way to stand up a new NiFi Registry instance and just point it
> at an existing git repo of flows.
> Currently the issue is that the git repo is only used for the persistence of
> flow content, and the metadata comes from a relational database, so if you
> lost your server and don't have a copy of the DB then the git repo alone
> isn't enough.
> In general the DB should be backed up, or an external DB with HA (Postgres)
> should be used instead of the H2 DB, but we should also be able to offer a
> way to bootstrap a new NiFi Registry instance from a git repo of flows.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
