falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Preece (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1095) Support free-text search for entities
Date Thu, 26 Mar 2015 22:09:52 GMT

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

Scott Preece commented on FALCON-1095:

I don't think there's a reasonable way to pull words out of names - too many people use different
conventions. You could havwe a configuration option, but I (a) not all schemes will readily
break out as words and (b) the people assigning names may not be the people who own the installation,
and (c) I don't know that most people would configure their installation to that extent, anyway.

I think there needs to be a good explanation for users of what the matching rules are, which
I didn't find, looking through the API documentation. I would probably take issue with subsequence
matching being well known, outside of a specific technical audience that is probably not typical
of data-management users. Wild-card matching is much more common thanks to use in the file
browsers in every OS.

Personally, I would rather use explicit wildcard indications, because it gives me more control,
but really I'm only asking that the method be made clear to users.

> 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

View raw message