Closed
Bug 1253360
Opened 8 years ago
Closed 8 years ago
Please whitelist the "AppInitDLLs" annotation
Categories
(Socorro :: General, task)
Socorro
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bugzilla, Assigned: adrian)
References
Details
Attachments
(1 file)
When bug 1240315 lands, Windows builds of Firefox will start generating an annotation called "AppInitDLLs" that is a string containing a list of files, delimited by semicolons. Could we whitelist this so that it can be displayed in the UI?
Updated•8 years ago
|
Assignee: nobody → adrian
Assignee | ||
Comment 1•8 years ago
|
||
What kind of operations do you expect to perform on this field in SuperSearch, if any? I'm asking to make sure I give it the best mapping in our Elasticsearch database. Note that it is already exposed, but I want to define a good mapping before marking this bug as resolved.
Assignee | ||
Comment 2•8 years ago
|
||
Example of what the data looks like in Super Search: https://crash-stats.mozilla.com/search/?product=Firefox&app_init_dlls=!__null__&_facets=app_init_dlls&_columns=date&_columns=app_init_dlls#facet-app_init_dlls
Comment 3•8 years ago
|
||
Well, for one thing, the current tokenization seems to treat "\" as a separator (maybe other characters as well), but only ";" seems to be an actually valid separator in this field.
Reporter | ||
Comment 4•8 years ago
|
||
Yes, ";" is the only valid delimiter. Each "token" is a filename that may or may not include a path. I don't know what kind of things you can do when it comes to mappings, but one thing that would be a "nice to have" is if we could search on the basename of each entry, so that I don't need to know the entire path of a file when searching.
Assignee | ||
Comment 5•8 years ago
|
||
Comment 6•8 years ago
|
||
Commit pushed to master at https://github.com/mozilla/socorro https://github.com/mozilla/socorro/commit/f9a84eb267c457c04adbec7891b7e4039f2da857 Bug 1253360 - Added a semicolon_keywords analyzer. r=peterbe
Assignee | ||
Comment 7•8 years ago
|
||
OK, this is done, the field should start behaving as expected next Monday.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•