Closed
Bug 1039969
Opened 10 years ago
Closed 10 years ago
Multiword search
Categories
(Socorro Graveyard :: Middleware, defect)
Socorro Graveyard
Middleware
Tracking
(Not tracked)
RESOLVED
FIXED
100
People
(Reporter: Yoric, Assigned: adrian)
References
Details
Using SuperSearch, I can search for all crashes in which field `async_shutdown_timeout` does not contain "experiments.jsm" (for some reason, I need to lowercase it), but if I search for all crashes in which the field does not contain "experiments.jsm shutdown", this fails to filter out anything.
The same issue appears when I search for all crashes in which a field contains "experiments.jsm shutdown", as this returns no crash.
Reporter | ||
Comment 1•10 years ago
|
||
Adrian, is this a well-known behavior? Is there a workaround?
Flags: needinfo?(adrian)
Assignee | ||
Comment 2•10 years ago
|
||
Can you please provide some URLs? Depending on how you use the API, it could be an expected behavior. For example, if you say ``async_shutdown_timeout=!~experiments.jsm%20shutdown`` that becomes a "phrase match", ie it looks from the phrase "experiments.jsm shutdown". The solution would be to use ``async_shutdown_timeout=!~experiments.jsm&async_shutdown_timeout=!~shutdown`` (that should work, if it doesn't then it's a bug).
Flags: needinfo?(adrian) → needinfo?(dteller)
Reporter | ||
Comment 3•10 years ago
|
||
Well, "phrase match" sounds good. The following query should return all the async_shutdown_timeout crashes that do not contain "experiments.jsm shutdown", shouldn't it?
https://crash-stats.mozilla.com/api/SuperSearch/?async_shutdown_timeout=!~experiments.jsm+shutdown&async_shutdown_timeout=!__null__
(this is the query built from the webapp) However, it returns crashes that contain "Experiments.jsm shutdown". I have also tried variants with `%20` instead of `+`, quotes, etc. it doesn't change anything.
Note that it works if I just use "experiments.jsm", rather than "experiments.jsm shutdown". Not if I use "Experiments.jsm", though.
Flags: needinfo?(dteller)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → adrian
Component: General → Middleware
Reporter | ||
Comment 4•10 years ago
|
||
Any news about this bug? This is blocking investigations on possible topcrashers.
Flags: needinfo?(adrian)
Assignee | ||
Comment 5•10 years ago
|
||
Pull request: https://github.com/mozilla/socorro/pull/2310
Flags: needinfo?(adrian)
Comment 6•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/socorro
https://github.com/mozilla/socorro/commit/f802be05d64f535307db53fc3c0ca3ea52393707
Fixes bug 1039969 - SuperSearch API now considers all arguments as lists.
https://github.com/mozilla/socorro/commit/ccdf7aa171791457fc2ab3794da4ec81bb28fadb
Merge pull request #2310 from AdrianGaudebert/1039969-api-supersearch-fields-are-lists
Fixes bug 1039969 - SuperSearch API now considers all arguments as lists.
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Target Milestone: --- → 100
Updated•8 years ago
|
Product: Socorro → Socorro Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•