1308474 - Add the new StartupCrash annotation to SuperSearch

Status: RESOLVED FIXED

(Socorro :: General, task)

Comment 1

[[DEACTIVATED] Adrian Gaudebert]

Added as `startup_crash`. See for example: https://crash-stats.mozilla.com/search/?product=Firefox&_facets=startup_crash&_columns=startup_crash#facet-startup_crash

Note that the mapping for this field has been changed, so its operators will only start working when we create a new Elasticsearch index next Monday.

Comment 2

[[DEACTIVATED] Adrian Gaudebert]

Wait, actually, what kind of data does this field have? Is it a string or is it a number? If it's 0 or 1, then we can turn that into a boolean, but if it's strings then that won't work.

Comment 3

[Marco Castelluccio [:marco]]

(In reply to Adrian Gaudebert [:adrian] from comment #2)
> Wait, actually, what kind of data does this field have? Is it a string or is
> it a number? If it's 0 or 1, then we can turn that into a boolean, but if
> it's strings then that won't work.

It's a string that can assume one of two values, '0' or '1', or be undefined.
It's similar to safe_mode, which we are turning into a boolean. The only
difference is that safe_mode is never undefined.

Comment 4

[[DEACTIVATED] Adrian Gaudebert]

OK, the `safe_mode` field seems to be working well, so I assume this one will go well too. Let's verify this next Monday! :)

Comment 5

[Lehych]

And could you add field desc to socorro:scripts/data/supersearch_fields.json ? Or this is not the correct place for one. Right now I'm experimenting with socorro installation with report and missing this field from 'socorro' index lead to exception on some reports pages.

Comment 6

[[DEACTIVATED] Adrian Gaudebert]

Lehych, you might to follow bug 1100354. I've move it up in my list. In the meantime, you might be able to solve your problem using our public API (see the bug).