Hey all, I have a tentative schema available in [this pr.](https://github.com/mozilla-services/mozilla-pipeline-schemas/pull/540) I've made a few changes to the above proposed schema: - Added a `reason` field that we can use to simplify pre/post adjust pings - Split `device` into `manufacturer` and `model` I'd also like confirmation that `seq` will be 0-indexed. Stefan, do the above changes sound good to you? Petru, is this all acceptable on your end? Note we need the schema to match exactly (i.e. the field name are _exactly_ the same, but the values can obviously change) or else they will be rejected from the pipeline.
Bug 1633568 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hey all, I have a tentative schema available in [this pr.](https://github.com/mozilla-services/mozilla-pipeline-schemas/pull/540) I've made a few changes to the above proposed schema: - Added a `reason` field that we can use to simplify pre/post adjust pings - Split `device` into `manufacturer` and `model` I'd also like confirmation that `seq` will be 0-indexed. Stefan, do the above changes sound good to you? Petru, is this all acceptable on your end? Note we need the schema to match [this example](https://github.com/mozilla-services/mozilla-pipeline-schemas/blob/cd55128fb4b67e8b21931d57a6f79b82637bab84/validation/telemetry/installation.1.sample.pass.json) exactly (i.e. the field name are _exactly_ the same, but the values can obviously change) or else they will be rejected from the pipeline.
Hey all, I have a tentative schema available in [this pr.](https://github.com/mozilla-services/mozilla-pipeline-schemas/pull/540) I've made a few changes to the above proposed schema: - Added a `reason` field that we can use to simplify pre/post adjust pings - Split `device` into `manufacturer` and `model`, like we did for `activation` and in Fenix I'd also like confirmation that `seq` will be 0-indexed. Stefan, do the above changes sound good to you? Petru, is this all acceptable on your end? Note we need the schema to match [this example](https://github.com/mozilla-services/mozilla-pipeline-schemas/blob/cd55128fb4b67e8b21931d57a6f79b82637bab84/validation/telemetry/installation.1.sample.pass.json) exactly (i.e. the field name are _exactly_ the same, but the values can obviously change) or else they will be rejected from the pipeline.