You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2019/06/26 14:00:03 UTC

[jira] [Closed] (NIFIREG-288) When a property references a Controller Service, store information about that service in registry

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

Mark Payne closed NIFIREG-288.
------------------------------
    Resolution: Won't Do

This already is handled by the Map of identifiers to ExternalControllerServiceReferences at the VersionedFlowSnapshot level.

> When a property references a Controller Service, store information about that service in registry
> -------------------------------------------------------------------------------------------------
>
>                 Key: NIFIREG-288
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-288
>             Project: NiFi Registry
>          Issue Type: Improvement
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 0.5.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When a Processor or a Controller Service references another Controller Service, the exported flow contains the UUID of that Controller Service. Upon import, this allows NiFi to connect that processor/service with the referenced Controller Service.
> However, if that Controller Service is inherited from outside of the flow that is versioned, there is no information about that service, such as Name, Type, or Bundle. If NiFi were to have that information, it could marry up the reference to an existing Controller Service.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)