[
https://issues.apache.org/jira/browse/NIFIREG-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende resolved NIFIREG-209.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.4.0
> 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
> Fix For: 0.4.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> 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)
