[
https://issues.apache.org/jira/browse/NIFIREG-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498386#comment-16498386
]
ASF GitHub Bot commented on NIFIREG-173:
----------------------------------------
GitHub user bbende opened a pull request:
https://github.com/apache/nifi-registry/pull/121
NIFIREG-173 Refactor metadata DB to be independent of H2
The approach here is to create a new DB with a schema and DataSource that
is not specific to H2 and migrate existing data.
During start up if the previous DB properties are populated and the new DB
has not been setup yet, then it initiate a migration of the data from the old
DB to new DB. For anyone starting up for the first time without the legacy DB
then it will just start with the new schema and DB.
I tested taking an existing 0.1.0 registry and dropping the old H2 DB into
a build of this PR and it migrated over to the new H2 DB and was able to
continue using the app as normal. Future restarts after that don't trigger the
migration since the new DB already exists at that point.
I also tested the same scenario as above, but using Postgres as the target
DB by copying the Postgres driver jar into the lib directory and configuring
the appropriate properties in nifi-registry.properties.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bbende/nifi-registry db-refactor
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-registry/pull/121.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 #121
----
commit b8ac082b0c0449a038aa09a38d67789e8b1559db
Author: Bryan Bende <bbende@...>
Date: 2018-05-30T18:31:26Z
NIFIREG-173 Refactor metadata DB to be independent of H2
----
> Allow metadata DB to use other DBs besides H2
> ---------------------------------------------
>
> Key: NIFIREG-173
> URL: https://issues.apache.org/jira/browse/NIFIREG-173
> Project: NiFi Registry
> Issue Type: Improvement
> Affects Versions: 0.1.0
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
>
> Now that we have the Git provider for flow storage which can be used to push
> flows to a remote location, it would be nice to be able to leverage an
> external DB for the metadata database.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
