[
https://issues.apache.org/jira/browse/NIFI-13961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-13961:
-------------------------------
Fix Version/s: 2.1.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add support for camelCase search on components
> ----------------------------------------------
>
> Key: NIFI-13961
> URL: https://issues.apache.org/jira/browse/NIFI-13961
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: endzeit
> Assignee: endzeit
> Priority: Minor
> Fix For: 2.1.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The search provided inside the NiFi UI for selecting a component, such as a
> Processor or ControllerService, queries for a literal match of the entered
> search term against the component's type, description and other fields.
> While this is very useful, it requires users to enter complete parts of the
> component type (or other information), without the support for fuzzy search.
> Let's use the following component type as an example:
> {{org.apache.nifi.processors.standard.GenerateFlowFile}}
> Users will find a lot of results when searching for "generate" or "FlowFile"
> as these are common terms referred to in the documentation of components. The
> same is true for other terms such as "record".
> This forces users to type longer parts of the component name, such as
> "GenerateF", or think about the end of the prefix which is not very
> intuitive, such as "ateFlo".
> The goal of this issue is to enhance the existing search functionality with a
> camelCase search functionality, similar to what developers might know from
> IDEs when searching for classes in code.
> The original search should not be affected.
> Users should find the above component when searching for the start characters
> of each capitalised word, such as "GeFlFi" or even "GFF" instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
