[
https://issues.apache.org/jira/browse/NIFIREG-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16351522#comment-16351522
]
Andrew Grande commented on NIFIREG-136:
---------------------------------------
Sure Kevin.
If we keep using UUIDs *internally*, that would allow for any renaming support.
The point really is shift the burden of dealing with uuids away from users, now
that they are exposed to how NiFi handled PG, etc.
The UUID has no meaning really when promoting to a different env (new bucket or
different registry instance). I would like to think in terms of:
# Copy this permalink of the flow version I want to promote.
# 'Paste' it into the new bucket and/or registry instance (e.g. DEV -> QA).
The target will be generating new uuids in any case (ideally transparently
behind the scenes just by determining that path doesn't exist).
Should it come to that, I can trade off Flow and Bucket names being immutable
for having shareable and friendly URIs.
> Switch to unique human-friendly names for buckets and flows
> -----------------------------------------------------------
>
> Key: NIFIREG-136
> URL: https://issues.apache.org/jira/browse/NIFIREG-136
> Project: NiFi Registry
> Issue Type: Improvement
> Affects Versions: 0.1.0
> Reporter: Andrew Grande
> Priority: Major
>
> I have been playing with the Registry and using [~bende] 's early CLI to
> accomplish some automation tasks. Have had really tough times with UUIDs
> being used for buckets and flows, it introduced a lot of context switches to
> locate/save/copy/paste those when using the API.
> I would strongly suggest considering the human-friendly names and convert
> deep links to using those instead. This not only provides for an easy
> portable full URI, but also addresses compatibility issues between instances
> of the registry, as buckets & flows with the same name are guaranteed to have
> different UUIDs. A kind of copy/paste between environments.
> I never came across a unique name requirement within a tree-like structure to
> be an issue when dealing with NiFi. E.g. NiFi and NiFi Registry could
> transparently reverse-look up the UUID by extracting names from the URI. The
> goal is to have a great user experience.
> P.S.: spaces in the name in the URI could be substituted for '+' sign
> transparently, using the %20 would defeat the purpose of smooth ease-of-use.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
