Closed
Bug 823688
Opened 13 years ago
Closed 13 years ago
Anomalies with search in reviewer tools
Categories
(Marketplace Graveyard :: Reviewer Tools, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 746764
People
(Reporter: krupa.mozbugs, Unassigned)
References
()
Details
Attachments
(1 file)
|
1.18 MB,
image/png
|
Details |
steps to reproduce:
1. In reviewer tools, search for "privileged app test123"
2. Notice the search results
expected behavior:
a) Search results are listed by relevancy and the app with that name is listed at the top of the search results.
b) Only matching search results are listed
observed behavior:
- App with the same name as the search query is listed below other apps
- Apps like "Lemonade" which do not match the search query are also listed.
Comment 1•13 years ago
|
||
FWIW, the search implementation just splits on whitespace and does text matching in the db. So it won't be able to sort by relevancy. It also searches by name and author which is possibly why "Lemonade" shows up b/c the author name has "test" in it.
Comment 2•13 years ago
|
||
(In reply to Rob Hudson [:robhudson] from comment #1)
> FWIW, the search implementation just splits on whitespace and does text
> matching in the db. So it won't be able to sort by relevancy. It also
> searches by name and author which is possibly why "Lemonade" shows up b/c
> the author name has "test" in it.
So this bug should be to make the reviewer tools use ES. Any reason not to?
Comment 3•13 years ago
|
||
which makes it a dupe or dependent on 746764?
Comment 4•13 years ago
|
||
It'd be great to use ES. The current search is a nice step as long as we acknowledge it's not using a full search implementation.
I'm curious if the problems I ran into earlier with the apps sometimes not showing up with the queues have cleared themselves up since we've done a lot of work with queues and signals lately.
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•