[
https://issues.apache.org/jira/browse/FALCON-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ying Zheng updated FALCON-1095:
-------------------------------
Description:
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. To be more specific, users can filter entities by type (i.e. feed and
process), regular expression that matches the name, and keywords in tags.
We plan to add a new API: GET api/entities/search
Parameters (all optional)
name Regular expression filter on name (e.g. name=fullname,
name=department.*). Not case sensitive.
type Valid options are feed and process.
tags AND filter on tags, separated by comma. Support substring
matching so the user doesn’t need to enter the full tag string.
orderBy Column by which results should be ordered. Default is “name”.
sortOrder Valid options are "asc" and “desc”. Default is “asc”.
offset Show results from the offset. Used for pagination. Default
is 0.
numResults Number of results to show per request. Used for pagination. Only
integers > 0 are valid. Default is 10.
e.g. falcon entity -search -name house.*texas -tags estate
This should return the entity with name "houseSellTexas" and tags
"category=realestate".
was:
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. To be more specific, users can filter entities by type (i.e. feed and
process), regular expression that matches the name, and keywords in tags.
We plan to add a new API: GET api/entities/search
Parameters (all optional)
name Regular expression filter on name (e.g. name=fullname,
name=department.*). Not case sensitive.
type Valid options are feed and process.
tags AND filter on tags, separated by comma. Support substring
matching so the user doesn’t need to enter the full tag string.
orderBy Column by which results should be ordered. Default is “name”.
sortOrder Valid options are "asc" and “desc”. Default is “asc”.
offset Show results from the offset. Used for pagination. Default
is 0.
numResults Number of results to show per request. Used for pagination. Only
integers > 0 are valid. Default is 10.
e.g. falcon entity -search -name house.*texas -tags estate
This should return entity with name "houseSellTexas" and tags
"category=realestate".
> 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
> 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. To be more specific, users can filter entities by type (i.e. feed
> and process), regular expression that matches the name, and keywords in tags.
> We plan to add a new API: GET api/entities/search
> Parameters (all optional)
> name Regular expression filter on name (e.g. name=fullname,
> name=department.*). Not case sensitive.
> type Valid options are feed and process.
> tags AND filter on tags, separated by comma. Support substring
> matching so the user doesn’t need to enter the full tag string.
> orderBy Column by which results should be ordered. Default is “name”.
> sortOrder Valid options are "asc" and “desc”. Default is “asc”.
> offset Show results from the offset. Used for pagination. Default
> is 0.
> numResults Number of results to show per request. Used for pagination. Only
> integers > 0 are valid. Default is 10.
> e.g. falcon entity -search -name house.*texas -tags estate
> This should return the entity with name "houseSellTexas" and tags
> "category=realestate".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
