nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aldrin Piri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-820) Provide improved provenance search functions for a component ID
Date Mon, 26 Oct 2015 01:59:27 GMT

    [ https://issues.apache.org/jira/browse/NIFI-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973552#comment-14973552
] 

Aldrin Piri commented on NIFI-820:
----------------------------------

0

Build, contrib, and code all looks good.  I was able to test it in the UI and all seemed good,
however, the provenance menu was also provided for processing groups, which of do not have
provenance events.  If there was some search that would span all nested components, I could
see the value, but this should likely be removed from the context menu in the interim.  Otherwise,
looks great and is a tremendous time saver.

> 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)

Mime
View raw message