Closed
Bug 1424411
Opened 8 years ago
Closed 7 years ago
Put a plan in place for removing activity_date from client_count_daily
Categories
(Data Platform and Tools Graveyard :: Datasets: Client Count, enhancement, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: relud, Assigned: relud)
References
Details
Attachments
(1 file)
Put a plan in for removing activity_date altogether (e.g. once 99.5% of pings have equivalent activity_dates and submission_dates).
as requested by :frank in 1380640
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → dthorn
Assignee | ||
Updated•8 years ago
|
Assignee | ||
Comment 1•8 years ago
|
||
as per bug 1422892 I think we should just remove activity_date from client_count_daily immediately, and let people know when they switch that they need to use `submission_date` instead of `activity_date`.
Frank, Mark, thoughts? objections? I saw :flod is using client_count_daily now in https://sql.telemetry.mozilla.org/queries/50134/source but I think that relatively few (maybe 4?) people have touched client_count_daily right now, so I think we would benefit from making this switch sooner rather than later.
Assignee | ||
Comment 2•8 years ago
|
||
> and let people know when they switch
switch from `client_count` to `client_count_daily`
Comment 3•8 years ago
|
||
(In reply to Daniel Thorn [:relud] from comment #1)
> as per bug 1422892 I think we should just remove activity_date from
> client_count_daily immediately, and let people know when they switch that
> they need to use `submission_date` instead of `activity_date`.
>
> Frank, Mark, thoughts? objections? I saw :flod is using client_count_daily
> now in https://sql.telemetry.mozilla.org/queries/50134/source but I think
> that relatively few (maybe 4?) people have touched client_count_daily right
> now, so I think we would benefit from making this switch sooner rather than
> later.
I think this is a good idea. We'll need two things:
1. Documentation describing how submission_date based client_counts have changed over time (e.g. when ping sender came into effect) such that they are now acceptable to use. We can then just point people at that documentation as they switch over
2. A version bump, and a backfill of all the old data
Flags: needinfo?(fbertsch)
Assignee | ||
Updated•8 years ago
|
Priority: P3 → P2
Assignee | ||
Updated•8 years ago
|
Priority: P2 → P1
Comment 4•8 years ago
|
||
This sounds like a good idea. Let's leave the v1 data in place so we can still do comparisons between submission date and activity date on historic data, and add v2 and backfill it per above.
Flags: needinfo?(mreid)
Comment 5•8 years ago
|
||
Assignee | ||
Comment 6•8 years ago
|
||
bumping this to a p2 so we can bikeshed bug 1434991 into the change
Priority: P1 → P2
Assignee | ||
Comment 7•7 years ago
|
||
client_count_daily now has this change
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Data Platform and Tools → Data Platform and Tools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•