[
https://issues.apache.org/jira/browse/FALCON-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536986#comment-14536986
]
Srikanth Sundarrajan commented on FALCON-1095:
----------------------------------------------
My 2 cents. The current proposal is to support the following as per FALCON-1121
{noformat}
Optional Args : -fields <<field1,field2>>
-nameseq <<namesubsequence>> -tagkey <<tagkeyword1,tagkeyword2>>
-filterBy <<field1:value1,field2:value2>> -tags
<<tagkey=tagvalue,tagkey=tagvalue>>
-orderBy <<field>> -sortOrder <<sortOrder>> -offset 0 -numResults 10
{noformat}
It seems to be getting very verbose and avoidable complex and may make it hard
for users to use this. I suggest we try and do something simpler and more
intuitive.
{noformat}
-filter "field:value,field2:value2..." - search
"free-text-to-search-anywhere-in-the-entity"
-orderBy <<field>> -sortOrder <<sortOrder>> -offset 0 -numResults 10
{noformat}
> 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
> schedulable. Here "schedulable" includes 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) tagkeys Tag keywords, separated by comma. Not case sensitive.
> The returning entities must have tags that match all the tag keywords.
> Results
> Return the total number of entity results and a list of entities.
> e.g. falcon entity -list -nameseq housetexas -tagkeys estate
> This should return the entity with name "houseSellTexas" and tags
> "category=realestate".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
