[
https://issues.apache.org/jira/browse/NIFIREG-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500402#comment-16500402
]
ASF GitHub Bot commented on NIFIREG-173:
----------------------------------------
Github user kevdoran commented on a diff in the pull request:
https://github.com/apache/nifi-registry/pull/121#discussion_r192790706
--- Diff: nifi-registry-docs/src/main/asciidoc/administration-guide.adoc ---
@@ -867,12 +867,32 @@ content of the flows saved to the registry. For
further details on persistence p
These properties define the settings for the Registry database, which
keeps track of metadata about buckets and all items stored in buckets.
+The 0.1.0 release leveraged an embedded H2 database that was configured
via the following properties:
+
|====
|*Property*|*Description*
|nifi.registry.db.directory|The location of the Registry database
directory. The default value is `./database`.
|nifi.registry.db.url.append|This property specifies additional arguments
to add to the connection string for the Registry database. The default value
should be used and should not be changed. It is:
`;LOCK_TIMEOUT=25000;WRITE_DELAY=0;AUTO_SERVER=FALSE`.
|====
+The 0.2.0 release introduced a more flexible approach which allows
leveraging an external database. This new approach
+is configured via the following properties:
--- End diff --
Good writeup. Clear and concise.
> 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)
