[
https://issues.apache.org/jira/browse/NIFI-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973559#comment-14973559
]
Matt Gilman commented on NIFI-820:
----------------------------------
Per a conversation with [~markap14] all components could be a source of
provenance events. Basically anything that's not a connection. I think the gist
may have been around who generates events for expiration/dropping/sending?/etc.
Or maybe the process group was just an oversight. Either way, it will be a
trivial adjustment. Mark?
> 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)
