[jira] [Commented] (NIFIREG-238) Support Registry URL Aliasing

["Bryan Bende (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFIREG-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792112#comment-16792112 ] 

Bryan Bende commented on NIFIREG-238:
-------------------------------------

Definitely interesting idea. Would the aliasing approach handle cases where the nested flow is actually pointing to a different registry?

So on NiFi side you have parent PG versioned controller at [http://registry-1.com|http://registry-1.com/] and then inside it child PG version controlled at [http://registry-2.com|http://registry-2.com/].

In registry-1 the versioned flow for the parent PG has the nested PG with the pointer its location, would that be aliased too somehow?

> Support Registry URL Aliasing
> -----------------------------
>
>                 Key: NIFIREG-238
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-238
>             Project: NiFi Registry
>          Issue Type: New Feature
>            Reporter: Bryan Rosander
>            Priority: Major
>
> It would be nice to be able to change the URL of a NiFi Registry without rewriting all flow history.
> In a deeply nested flow where there are dependencies on potentially multiple versions of the same process group, this doesn't seem to be possible. (You can update the URL in the latest version but cannot retroactively change it for the benefit of process groups pointing at the older version(s).)
> If we allowed for aliasing of that field, this would be a non-issue, it could be stored as a token (or original url) inside the registry and rewritten when requested.  When persisting, it could be translated back to the token value.
>  



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