Closed
Bug 1411397
Opened 8 years ago
Closed 8 years ago
error_aggregates improperly parsing displayVersion
Categories
(Data Platform and Tools Graveyard :: Datasets: Error Aggregates, enhancement, P1)
Data Platform and Tools Graveyard
Datasets: Error Aggregates
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: frank, Assigned: wlach)
References
Details
Exception:
org.json4s.package$MappingException: No usable value for application
No usable value for displayVersion
Did not find value which can be converted into java.lang.String
Updated•8 years ago
|
Points: --- → 1
Priority: -- → P1
| Assignee | ||
Comment 1•8 years ago
|
||
Apparently "displayVersion" is not currently required by the pipeline schema.
https://github.com/mozilla-services/mozilla-pipeline-schemas/blob/961d24db526c9a0e90785ac50f3b08e6d46800b4/schemas/telemetry/main/main.4.schema.json#L39
Should it be? And if so, should we just skip pings (from older "versions" of Firefox) that don't have the value?
Flags: needinfo?(mreid)
Comment 2•8 years ago
|
||
Looks like it was added in Fx 46, so I think it's fine for Mission Control to skip pings that don't have it, however I don't think we can reject them at ingestion / schema validation time.
I'm not sure if the same is true for the error aggregates dataset, but it seems unlikely we'll do anything about errors prior to 46.
If we do want to keep these pings, we could fall back to application.version if application.displayVersion is missing.
Flags: needinfo?(mreid)
| Reporter | ||
Updated•8 years ago
|
Component: Datasets: General → Datasets: Error Aggregates
Depends on: 1388351
| Assignee | ||
Comment 3•8 years ago
|
||
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Data Platform and Tools → Data Platform and Tools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•