[
https://issues.apache.org/jira/browse/NIFIREG-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352555#comment-16352555
]
Bryan Bende commented on NIFIREG-136:
-------------------------------------
I like the idea of having a way to reference the bucket and flow by their
names, but we also can't just change the meaning of the existing end-point as
the NiFi integration with registry is already built using the UUID based API
(plus anyone who else may have built something). I'd prefer to create some
alternative way to access by name, such that both approaches could co-exist.
Currently we have:
{code:java}
/buckets/{uuid}/flows/{uuid}/versions/{version|latest}{code}
Could we do something like:
{code:java}
/buckets/n={name}/flows/n={name}/versions/{version|latest}{code}
This way there is some indication that we are using names instead of UUIDs.
Also, just wanted to mention that the item name is only unique per bucket, so
two different flows named "Bryan's Flow" can exist in bucket1 and bucket2. I'm
only mentioning this because it means we can't access a flow by name without
the bucket id.
> 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)
