[
https://issues.apache.org/jira/browse/NIFIREG-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669175#comment-16669175
]
ASF GitHub Bot commented on NIFIREG-209:
----------------------------------------
Github user kevdoran commented on the issue:
https://github.com/apache/nifi-registry/pull/144
This is a fun new feature @bbende. It will be nice for DR or as a mechanism
to populate NiFi Registry instances in new environments with some canned flows.
I looked at the code and tried it out and it's working well for me. There is
some oddness when loading flows from 0.2.0 or 0.3.0 as they don't have all the
metadata available, but I think that's fine. Going forward with git repos
created after this feature exists should have everything there.
Interested to hear from @ijokarumawak on this to get his input as he is the
most experienced with the Java Git stuff, but consider me a tentative +1 on
this PR. Cool stuff!
> 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)
