Closed Bug 1174925 Opened 9 years ago Closed 7 years ago

Handle UT Deletion ping in pipeline

Categories

(Data Platform and Tools :: General, defect, P3)

Product:
Data Platform and Tools
Component:
General
Type:
defect
Points:
2

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1445921

People

(Reporter: kparlante, Assigned: mreid)

References

Details

(Whiteboard: [unifiedTelemetry][rC])

Current decision for handling delete pings in the pipeline: - Remove from clientId indexes - No other special treatment, pings are removed from the server as they age out due to the retention policy
This bug will be for the implementation of the policy. Another bug for policy approval to follow.
Assignee: nobody → mreid
Priority: -- → P2
Whiteboard: [unifiedTelemetry][b5]
Whiteboard: [unifiedTelemetry][b5] → [unifiedTelemetry][rC]
Iteration: --- → 43.1 - Aug 24
Goes along with other clientId work
Priority: P2 → P3
Given the current approach to longitudinal analysis as described in Bug 1242039, I propose the following: When generating the data set for longitudinal analysis, omit any clientIds for whom the most recently seen submission is a "deletion" ping. This should remove any opted-out clientIds from longitudinal analysis, as well as handling the case where a clientId opts out then back in (toggling Telemetry off/on once or more). Benjamin, as a data peer does this sound reasonable?
Flags: needinfo?(benjamin)
As long as "most recent" can be handled sanely in a parallel environment, sure.
Flags: needinfo?(benjamin)
Points: --- → 2
Priority: P3 → P2
Depends on: 1311483
Iteration: 43.1 - Aug 24 → ---
Component: Metrics: Pipeline → Datasets: General
Priority: P2 → P3
Product: Cloud Services → Data Platform and Tools
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Component: Datasets: General → General
You need to log in before you can comment on or make changes to this bug.