[
https://issues.apache.org/jira/browse/NIFIREG-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende moved NIFI-6383 to NIFIREG-285:
-------------------------------------------
Workflow: jira (was: patch-available, re-open possible)
Key: NIFIREG-285 (was: NIFI-6383)
Project: NiFi Registry (was: Apache NiFi)
> Implement a database FlowPersistenceProvider
> --------------------------------------------
>
> Key: NIFIREG-285
> URL: https://issues.apache.org/jira/browse/NIFIREG-285
> Project: NiFi Registry
> Issue Type: Improvement
> Reporter: Bryan Bende
> Priority: Major
>
> We currently have the options of local filesystem and git for flow storage.
> While git is for pushing to a remote and visualizing in github, it is only a
> one way push and not ideal for an HA scenario where we would want multiple
> instances of the NiFi Registry application running.
> We should implement a FlowStorageProvider backed by a relational database
> table that could live in the same DB as the metadata database. This would
> allow multiple NiFi Registry instances to run pointing at the same external
> database.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
