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/04/25 16:29:00 UTC

[jira] [Resolved] (NIFIREG-251) Track names of external controller service references for resolution on import

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

Bryan Bende resolved NIFIREG-251.
---------------------------------
    Resolution: Fixed

> Track names of external controller service references for resolution on import
> ------------------------------------------------------------------------------
>
>                 Key: NIFIREG-251
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-251
>             Project: NiFi Registry
>          Issue Type: Improvement
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Minor
>             Fix For: 0.4.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We should update the data model to provide a way to track the names of controller service references that are external to the versioned flow. Currently we end up with a VersionedPropertyDescriptor where the value is the service id and the boolean identifiesControllerService, but that id won't exist in any other environment so having the name somewhere would help if we want to implement a convention for resolving these references in NiFi.



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