Closed Bug 1321404 Opened 8 years ago Closed 7 years ago

Remove Churn view from telemetry-batch-view

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: amiyaguchi, Assigned: amiyaguchi)

References

Details

Attachments

(1 file)

As of recently, the notebook that generates the churn/retention dataset for analysis [1] no longer depends on the Churn view [2]. This view of the data should be pruned. This would require turning off any scheduled jobs that depend on this view, if they exist.


[1] https://github.com/mozilla/churn-analysis/commit/5917d71350eebb0e67e1b0e89edd6c9355933a15
[2] https://github.com/mozilla/telemetry-batch-view/blob/6d287a6c538bf62161bfd6a6413765138f57e418/src/main/scala/com/mozilla/telemetry/views/Churn.scala
Assignee: nobody → amiyaguchi
There is now a lot of potentially unused data under `telemetry-parquet/churn/v1`. Will we keep this around or clean it up eventually?
Flags: needinfo?(mreid)
Points: --- → 1
Priority: -- → P1
Once bug 1321414 has landed and we've verified that everything is working fine based on the main_summary data, we can safely remove the churn data in the telemetry-parquet bucket.
Flags: needinfo?(mreid)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Blocks: 1350126
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: