Closed
Bug 1351815
Opened 7 years ago
Closed 7 years ago
[churn][churn_to_csv] Set start date 10 days in the past
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
(2 files)
The current churn and churn_to_csv notebooks expects the date passed into it is the same date that is scheduled. This is inconsistent with airflow's behavior, which passes a start date that is a week behind the scheduled date. The churn jobs currently set the date back 17 days: 10 for data collection stabilization, and 7 days to account for the collection period from start to end dates. These jobs should expect a date that is already accounts for the week of data that needs to be collected from the start to end dates of the job.
Assignee | ||
Comment 1•7 years ago
|
||
Assignee | ||
Comment 2•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Points: --- → 1
Priority: -- → P1
Assignee | ||
Updated•7 years ago
|
Status: NEW → 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
•