markobean commented on PR #6949:
URL: https://github.com/apache/nifi/pull/6949#issuecomment-1444491910
> > Actually, I'm starting to think "N/A" really is the way to go. The
reason is that when you put `Label` (or presumably `Label-$UUDPrefix`) into the
search field, you get no results. I can see users expecting to get results when
they enter the "Name" value into the search. (I think we ought to add a "go to"
link in the NiFi History table too, now that I think about it.)
>
> The search behavior is worth considering, but that is outside of the Flow
Configuration History, so that seems like less of a concern than being able to
distinguish items in the Flow Configuration History view itself. The Flow
Configuration History can be filtered on Component ID or User, unfortunately
filtering on Name is not an option right now, but that could also be improved.
>
> I agree that adding a link from the History row to the component would be
very helpful.
Ok, now I understand the motivation for a unique "Name" better when put in
the context of the NiFi History, aka Flow Configuration History view itself. So
humor me and assume UUID is a column in that table. Choose your poison
("poison" meaning there will be inherent redundancy): `Lable-$UUDPrefix` or
straight `UUID`. If uniqueness is the goal, the latter would be a better choice.
If you agree, I'll make that update this weekend.
And, to be clear the "go to" as well as UUID in the history table is out of
scope for this particular PR; we'll cover that in separate ticket(s).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
