[
https://issues.apache.org/jira/browse/FALCON-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485393#comment-14485393
]
Mahak commented on FALCON-1095:
-------------------------------
As a suggestion, I'd recommend searching feeds on the basis of source and
target paths.
For the following reasons:
1. When there are a lot of feeds, users don't tend to remember the name of the
feeds necessarily however they do remember the directories that are fed by some
feed/process. This might be an assumption on my side but I did discuss it with
some of my colleagues and they share the same thought.
2. I'm not sure if Falcon has this feature, but when a feed, with a target path
already fed by some other scheduled feed, is submitted an error must be
generated stopping this new feed from being submitted. For such a feature, the
aforementioned search capability would come in handy.
> 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
> Labels: falcon-syncup
> 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) 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)
