Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Date: Sat, 14 Mar 2015 03:21:38 +0000 (UTC)
From: "Ajay Yadava (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12781927.1426282666000.92940.1426303298509@Atlassian.JIRA>
In-Reply-To: <JIRA.12781927.1426282666000@Atlassian.JIRA>
References: <JIRA.12781927.1426282666000@Atlassian.JIRA>
 <JIRA.12781927.1426282666849@arcas>
Subject: [jira] [Commented] (FALCON-1095) Support free-text search for
 entities
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/FALCON-1095?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D143=
61562#comment-14361562 ]=20

Ajay Yadava commented on FALCON-1095:
-------------------------------------

API to search for an entity already exists. It will help if you can illustr=
ate the advantages of your proposal over the existing implementation becaus=
e It will be a backward incompatible change to users who will get used to e=
xisting search scheme. From the example you have quoted it doesn't look any=
 different.

+1 for extending it to tags.=20

> 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 n=
ame 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 i=
n tags.
> We plan to add a new API: GET api/entities/search
> Parameters (all optional)
> name             Regular expression filter on name (e.g. name=3Dfullname,=
 name=3Ddepartment.*). Not case sensitive.
> type               Valid options are feed and process.
> tags               AND filter on tags, separated by comma. Support substr=
ing matching so the user doesn=E2=80=99t need to enter the full tag string.
> orderBy         Column by which results should be ordered. Default is =E2=
=80=9Cname=E2=80=9D.
> sortOrder       Valid options are "asc" and =E2=80=9Cdesc=E2=80=9D. Defau=
lt is =E2=80=9Casc=E2=80=9D.
> offset             Show results from the offset. Used for pagination. Def=
ault 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 "catego=
ry=3Drealestate".


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