[
https://issues.apache.org/jira/browse/NIFI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698466#comment-14698466
]
Matt Gilman commented on NIFI-828:
----------------------------------
[~Jon Anderson] Sure no problem. The applyFilter function is invoked whenever
the user does something. Currently that is selecting something from the combo,
typing in the filter field, and selecting a term from the tag cloud. The filter
function is registered with the grid to filter (line 910). So in applyFilter
all that happens is that args to filter function are updated and the grid data
is refreshed.
In this case, we're not going to be filtering based on a specific column so I
think we can just remove the property all together. That filter argument object
is passed to the filter function through the grid. So we'll need to update the
filter function to remove the references to args.property and instead search
both the name and the tags based on their field in each row.
Once this is done, we'll need to the same changes on the new Controller Service
and Reporting Task dialog too.
FYI - when you build you can disable the minify-and-compress profile in order
to have the JS more readable. This will allow you to easily debug everything
using your browser's developer tools.
> Update default filter in new Processor Dialog
> ---------------------------------------------
>
> Key: NIFI-828
> URL: https://issues.apache.org/jira/browse/NIFI-828
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Priority: Trivial
> Fix For: 0.3.0
>
> Attachments: 0001-NIFI-828.patch
>
>
> Update the default filter in the new processor dialog to use 'by tag' instead
> of 'by name'. A user will likely want to search for items using terms tagged
> on the processor rather than the formal processor name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
