[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=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)
[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=16669718#comment-16669718 ] ASF GitHub Bot commented on NIFIREG-209: Github user ijokarumawak commented on the issue: https://github.com/apache/nifi-registry/pull/144 Oh, this is going to be very useful! I'm reviewing now. Thanks! > 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)
[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=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)
[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=16669134#comment-16669134 ] ASF GitHub Bot commented on NIFIREG-209: Github user bbende commented on the issue: https://github.com/apache/nifi-registry/pull/144 @kevdoran @ijokarumawak what do you guys think of this? > 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)
[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=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 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)
