[
https://issues.apache.org/jira/browse/NIFI-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831233#comment-16831233
]
Bryan Bende commented on NIFI-5658:
-----------------------------------
I think there is a lot to consider here, and we need to more clearly define
how/where end-users will use this information.
If we are talking about the Add Processor, Add Controller Service, Add
Reporting Task windows, then we need to define what the UX is... where is each
piece of new information shown? how would a user filter or select on one of
these fields? etc.
> Build list of processors with various attributes at startup
> -----------------------------------------------------------
>
> Key: NIFI-5658
> URL: https://issues.apache.org/jira/browse/NIFI-5658
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework, Extensions
> Affects Versions: 1.7.1
> Reporter: Andy LoPresto
> Assignee: Troy Melhase
> Priority: Major
> Labels: component, security, tag
>
> There are some attributes of processors that are useful to expose to users.
> Qualities like "contains sensitive property descriptor(s)", "has required
> property descriptor(s) with no default value", "uses Controller Service X",
> etc. can help users categorize these components.
> Rather than require annotations (which requires a code change and release to
> update), Bryan Bende brought up querying these attributes at startup (NAR
> loading) and building simple lists/maps contained in memory.
> Exposing these collections can help with searching/filtering processors in
> the *Add Processor* dialog, understanding immediate needs on template import
> / versioned flow snippet import, etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
