[
https://issues.apache.org/jira/browse/NIFI-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973573#comment-14973573
]
Matt Gilman commented on NIFI-820:
----------------------------------
Agreed. Especially now that users can drop the flow files manually it may make
sense for them to be th source of an event. I'm thinking the process group
thing may have been a oversight in our conversation. Unfortunately, the term
component can be overloaded at times. I'll update the patch accordingly when/if
necessary.
> Provide improved provenance search functions for a component ID
> ---------------------------------------------------------------
>
> Key: NIFI-820
> URL: https://issues.apache.org/jira/browse/NIFI-820
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Reporter: Aldrin Piri
> Assignee: Matt Gilman
> Priority: Minor
> Fix For: 0.4.0
>
> Attachments: 0001-NIFI-820.patch, provenance context entry.png,
> provenance search auto suggest.png
>
>
> In terms of making provenance more accessible, it would be nice to have a
> provenance search via the processor context menu which auto populates the
> provenance with the processor ID. Typically when I want evaluate how a
> processor is behaving, I have to select configure, copy ID, hit provenance,
> paste the component ID.
> In a related fashion, providing the functionality of the search of main
> workflow in the component ID field of the provenance dialog to discover
> component ID could also prove to be useful.
> Not sure which of these makes sense, is feasible, or is actually an improved
> user experience, but each feels like it could expedite the process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
