Since we're now doing a hard cutover from main to events pings, we'll need to add events from Events pings to the events dataset to prevent disruption to event users' workflows. The dataset is already partitioned by docType, so we can write into docType=event with a schema matched to the current events dataset schema.
Current timeline on client side is to get event pings sent from Nightly63 first, then after enough days' data shows up for validation (bug 1463410), have it uplifted (so, to 62b2/b3).
Fixed with: https://github.com/mozilla/telemetry-streaming/pull/149 https://github.com/mozilla/telemetry-batch-view/pull/447 https://github.com/mozilla/telemetry-airflow/pull/319
Assignee: nobody → ssuh
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.