[
https://issues.apache.org/jira/browse/NIFIREG-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792116#comment-16792116
]
Bryan Rosander commented on NIFIREG-238:
----------------------------------------
Good point, I'd initially thought about nesting only in context of a single
registry holding nested flows.
In order for it to work with multiple registries, I'd think that you'd need to
keep some mapping of token -> registry url that would be synced for all
registries in a given environment?
If registry-1 has a pg that points to registry-2 which has a pg that points to
registry-1, they'd both need to know to alias the other for this to work when
going from one environment to another...
> 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)
