You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/30 18:06:00 UTC

[jira] [Commented] (NIFIREG-209) Support rebuilding metadata DB from Git repo

    [ https://issues.apache.org/jira/browse/NIFIREG-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669133#comment-16669133 ] 

ASF GitHub Bot commented on NIFIREG-209:
----------------------------------------

GitHub user bbende opened a pull request:

    https://github.com/apache/nifi-registry/pull/144

    NIFIREG-209 Rebuild metadata DB from FlowPersistenceProvider when emp…

    …ty DB AND when instance of MetadataAwareFlowPersistenceProvider

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bbende/nifi-registry git-sync

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi-registry/pull/144.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #144
    
----
commit 8f2ba56b8a331ee24d0e573f438eddf8d0152477
Author: Bryan Bende <bb...@...>
Date:   2018-10-30T01:35:12Z

    NIFIREG-209 Rebuild metadata DB from FlowPersistenceProvider when empty DB AND when instance of MetadataAwareFlowPersistenceProvider

----


> 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)