You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Simon Bence (Jira)" <ji...@apache.org> on 2022/09/13 16:38:00 UTC
[jira] [Updated] (NIFI-10497) Making RegistryClient an extension point

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

Simon Bence updated NIFI-10497:
-------------------------------
    Description: 
Currently NiFi is capable to connect only to the NiFi Registry as a "registry repository". It would be beneficial to give NiFi the capability to depend on other services.

In order to this, I suggest to decouple the registry behaviour from the NiFi Registry as much as it is possible (inlcuding but not only the API and the Resources) and move the actual implementation behind this new API.

To be able to add new implementations, this new API must be an extension point applying the usual NiFi instruments for this. Also it is paramunt to keep the continuity with the current usages and make the implementation capable to process the current REST call format. 

> Making RegistryClient an extension point
> ----------------------------------------
>
>                 Key: NIFI-10497
>                 URL: https://issues.apache.org/jira/browse/NIFI-10497
>             Project: Apache NiFi
>          Issue Type: New Feature
>         Environment: Currently NiFi is capable to connect only to the NiFi Registry as a "registry repository". It would be beneficial to give NiFi the capability to depend on other services.
> In order to this, I suggest to decouple the registry behaviour from the NiFi Registry as much as it is possible (inlcuding but not only the API and the Resources) and move the actual implementation behind this new API.
> To be able to add new implementations, this new API must be an extension point applying the usual NiFi instruments for this. Also it is paramunt to keep the continuity with the current usages and make the implementation capable to process the current REST call format. 
>            Reporter: Simon Bence
>            Assignee: Simon Bence
>            Priority: Critical
>
> Currently NiFi is capable to connect only to the NiFi Registry as a "registry repository". It would be beneficial to give NiFi the capability to depend on other services.
> In order to this, I suggest to decouple the registry behaviour from the NiFi Registry as much as it is possible (inlcuding but not only the API and the Resources) and move the actual implementation behind this new API.
> To be able to add new implementations, this new API must be an extension point applying the usual NiFi instruments for this. Also it is paramunt to keep the continuity with the current usages and make the implementation capable to process the current REST call format. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)