Closed Bug 1410161 Opened 7 years ago Closed 4 years ago

Get sync_ping_schema.json into mozilla-pipeline-schemas

Categories

(Firefox :: Sync, enhancement, P3)

enhancement

Tracking

()

RESOLVED INVALID

People

(Reporter: tcsc, Unassigned)

Details

This would probably have caught a number of issues we've encountered with our telemetry, since we'd get alerted on failures to pass the schema.

Unfortunately, it can't actually land as-is, since what we actually accept is much more generous than the schema specified there. If we were to land without updating it, it would complain a great deal, and also throw out most records from iOS and Android, both of which aren't as good at following the ping schema as Desktop (yay).

The schema should be updated to reflect the real schema accepted by the SyncPingConversion.scala code, and then incorporated into https://github.com/mozilla-services/mozilla-pipeline-schemas.
Summary: Get sync_ping_schema.json mozilla-pipeline-schemas → Get sync_ping_schema.json into mozilla-pipeline-schemas
Do you want to take this one, Thom?
Flags: needinfo?(tchiovoloni)
Yep, but I'll leave it as P2 since it's not critical.
Assignee: nobody → tchiovoloni
Flags: needinfo?(tchiovoloni)
Priority: -- → P2
For the reasons mentioned above (we can't land as-is so really this bug is "write a new schema that accurately reflects what SyncPingConversion.scala accepts"), this is getting pushed to he back burner (and I'm unassigning it from myself).

In the future it should be easier due to the release version of more clients sending acceptable schemas anyway.
Assignee: tchiovoloni → nobody
Priority: P2 → P3

The pipelines have all changed.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.