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

Scott Preece commented on FALCON-1095:
--------------------------------------

Perhaps I misunderstand what this does. In IntelliJ, I can find a class named 
"HCatPartitionManipulator" by searching for "partman". However, a search for 
"parttor" won't find it. [It looks like it understands camel case and is only 
searching on prefixes of the capitalized words in the class name.] My 
understanding of the description in this JIRA was the equivalent of putting a 
"*" after each character in the in a glob, which would match any string that 
contained the pattern characters in the given order.

Under that interpretation, matching would get false positives when a character 
appeared in the right order, but in an intervening word of the name - like 
looking for "parttor" and finding "PathReturningNonstandardFormat", where the 
letters happen to appear in the given order, but bear no resemblance to the 
expected result. Maybe it doesn't matter - maybe people tend to construct 
queries out of prefix strings with longer substrings, for instance.

In any case,there should be a detailed explanation in the documentation...

> Support free-text search for entities
> -------------------------------------
>
>                 Key: FALCON-1095
>                 URL: https://issues.apache.org/jira/browse/FALCON-1095
>             Project: Falcon
>          Issue Type: New Feature
>    Affects Versions: 0.6
>            Reporter: Ying Zheng
>            Assignee: Ying Zheng
>             Fix For: 0.7
>
>
> When users have hundreds or thousands of entities to manage, they may not 
> remember the exact name/tag of the entity. We would like to provide a more 
> convenient way for the user to search an entity by providing keywords in name 
> and tags. We also plan to provide a search UI, similar to Visual Search, to 
> allow the user to enter keywords in a search box and display the filtered 
> results. The user can click on the entity to view details and search its 
> instances as well.
> To support free-text search, we plan to extend the LIST API:
> GET api/entities/list/:entity-type
> Parameters changed/added:
>     1) :entity-type  Valid options are cluster, feed, process and all. Here 
> "all" represents feeds and processes.
>     2) nameseq     Subsequence of entity name. Not case sensitive. Example: 
> "Sample1" is a subsequence of entity name "SampleFeed1". Note that we rename 
> "pattern" parameter to "nameseq" to make it more intuitive to the user, but 
> the functionality is already there in Falcon-914 .
>     3) tagkey         Tag keywords, separated by comma. Not case sensitive.
> Results
>     Return the total number of entity results and a list of entities.
> e.g. falcon entity -list -nameseq housetexas -tagkey estate
> This should return the entity with name "houseSellTexas" and tags 
> "category=realestate".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to