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

Posted to issues@nifi.apache.org by "Bryan Bende (JIRA)" <ji...@apache.org> on 2019/07/17 20:08:00 UTC

[jira] [Assigned] (NIFIREG-285) Implement a database FlowPersistenceProvider

     [ https://issues.apache.org/jira/browse/NIFIREG-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Bende reassigned NIFIREG-285:
-----------------------------------

    Assignee: Bryan Bende

> 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
>            Assignee: Bryan Bende
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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.14#76016)