Closed
Bug 1337037
Opened 7 years ago
Closed 7 years ago
Add stub attribution field to retention dataset
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: amiyaguchi, Assigned: amiyaguchi)
References
Details
Attachments
(1 file)
The attribution field was added to the main summary in bug 1331082. This field belongs in the retention dataset because it helps follow clients over time in cohorts. I have created an example redash query that will feed from this data source.[1] [1] https://sql.telemetry.mozilla.org/queries/2655
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → amiyaguchi
Assignee | ||
Updated•7 years ago
|
Status: NEW → UNCONFIRMED
Ever confirmed: false
Priority: -- → P1
Assignee | ||
Comment 1•7 years ago
|
||
I've added the stub attribution fields to the churn dataset. However, there are a few things that need to be verified before I go ahead and make the pull request. This exploratory notebook [1] explains how the data has changed with the new update. [1] https://gist.github.com/acmiyaguchi/f21a92b2980e177ab7fc4468c0c55074
Assignee | ||
Comment 2•7 years ago
|
||
I have updated the private bucket location [1] and backfilled it with data since 01-01-2017. You can access the data through redash [2] for exploration. There is some logic in bug 1309290 comment 1 that should be integrated here. [1] s3://net-mozaws-prod-us-west-2-pipeline-analysis/amiyaguchi/churn_testing/ [2] https://sql.telemetry.mozilla.org/queries/3372/source#table
Assignee | ||
Comment 3•7 years ago
|
||
Assignee | ||
Comment 4•7 years ago
|
||
Data has been backfilled to 20160306.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•