[
https://issues.apache.org/jira/browse/NIFI-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567673#comment-14567673
]
Matt Gilman commented on NIFI-582:
----------------------------------
Miriam,
The wording that is used is typically influenced by the context in which its
being used. Below is a quick explanation of each concern.
Configuration/Detail Dialogs
- We just refer to the value as 'Id' here as there is no other distinction that
is necessary. It's the identifier of component being configured/viewed.
Flow Configuration History
- For actions on a specific component, we use the label 'Id'. When the
component is a connection, we use 'Id' for the connection itself. We also show
the details (Id, Name, Type) for the source and destination components. These
are labeled 'Source Id' and 'Destination Id'. However, it does appear that the
label in the filter dialog does say 'by source id'. The intent was that it was
the source of the action but I can see that being confusing when the component
in question is a connection. That should probably just read 'by id'. I will
address that in this ticket.
Data Provenance
- The context for this dialog is a provenance event. Part of the details of a
provenance event is the component that generated it. These fields are labeled
'Component Id', 'Component Name', and 'Component Type'. Simply naming them
'Id', 'Name', and 'Type' would suggest they are the Id, Name, and Type of the
event and could potentially conflict with other fields like the provenance
event type (SEND, ROUTE, DROP, etc).
Let me know if there are any other questions/concerns. Thanks!
> Inconsistent naming convention of IDs for the same component in NiFi UIs
> ------------------------------------------------------------------------
>
> Key: NIFI-582
> URL: https://issues.apache.org/jira/browse/NIFI-582
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 0.0.2
> Reporter: Miriam Kimball
> Priority: Minor
> Labels: DataProvenance, FlowConfigHistory
>
> In the Processor Details and Connection Details UIs, the unique ID is labeled
> "Id".
> In the Data Provenance UI, the same ID is labeled "Component Id".
> In the Flow Configuration History UI, the same ID is labaled "Source ID".
> The Data Provenance UI is the one that's confusing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
