[
https://issues.apache.org/jira/browse/NIFIREG-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende resolved NIFIREG-238.
---------------------------------
Resolution: Fixed
Assignee: Bryan Rosander
Fix Version/s: 0.4.0
> 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
> Assignee: Bryan Rosander
> Priority: Major
> Fix For: 0.4.0
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> 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)
