atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qiang Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-1261) Support fuzzy query in web Search
Date Wed, 02 Nov 2016 08:05:58 GMT

     [ https://issues.apache.org/jira/browse/ATLAS-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Qiang Zhang updated ATLAS-1261:
-------------------------------
    Description: 
use SEARCH in web page, find that our search policy cannot support fuzzy query.
eg:  Stored data to three tables, such as login_dept1, login_dept2, login_dept3. 
There are three scenarios: 

1. When  SEARCH condition is "login_dept", can't display any result.

2. When SEARCH condition is "login_dept*", can display  three tables information ( login_dept1,
login_dept2, login_dept3 ).

3. When  SEARCH condition is "login__dept1", can display one table information (login_dept1).

It would be convenient for users to provide fuzzy query by default, because ordinary users
may not be aware of using fuzzy query by wildcard character(“*”).  meanwhile it may consumption
query speed.

We can have a discussion that whether it is necessary to add wildcard character(“*”)
in our default SEARCH condition automatically?

  was:
use SEARCH in web page, find that our search policy cannot support fuzzy query.
eg:  Stored data to three tables, such as login_dept1, login_dept2, login_dept3. 
There are three scenarios: 

1. When  SEARCH condition is "login_dept", can't display any result.

2. When SEARCH condition is "login_dept*", can display  three tables information ( login_dept1,
login_dept2, login_dept3 ).

3. When  SEARCH condition is "login__dept1", can display one table information (login_dept1).

It would be convenient for users to provide fuzzy query by default, because ordinary users
may not be aware of using fuzzy query by wildcard character(*).  meanwhile it may consumption
query speed.

We can have a discussion that whether it is necessary to add wildcard character(*) in our
default SEARCH condition automatically?


> Support fuzzy query in web Search
> ---------------------------------
>
>                 Key: ATLAS-1261
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1261
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Qiang Zhang
>
> use SEARCH in web page, find that our search policy cannot support fuzzy query.
> eg:  Stored data to three tables, such as login_dept1, login_dept2, login_dept3. 
> There are three scenarios: 
> 1. When  SEARCH condition is "login_dept", can't display any result.
> 2. When SEARCH condition is "login_dept*", can display  three tables information ( login_dept1,
login_dept2, login_dept3 ).
> 3. When  SEARCH condition is "login__dept1", can display one table information (login_dept1).
> It would be convenient for users to provide fuzzy query by default, because ordinary
users may not be aware of using fuzzy query by wildcard character(“*”).  meanwhile it
may consumption query speed.
> We can have a discussion that whether it is necessary to add wildcard character(“*”)
in our default SEARCH condition automatically?



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

Mime
View raw message