Closed
Bug 1169367
Opened 10 years ago
Closed 4 years ago
Combine event hit stats
Categories
(Webtools Graveyard :: Air Mozilla, defect, P2)
Webtools Graveyard
Air Mozilla
Tracking
(firefox41 affected)
RESOLVED
INVALID
| Tracking | Status | |
|---|---|---|
| firefox41 | --- | affected |
People
(Reporter: peterbe, Unassigned)
References
Details
When we query Vid.ly for hits, we communicate by saying the Vid.ly shortcode (e.g. abc123). They give us a number (e.g. 12,345) of hits.
We record this in EventHitStats which looks like this: https://github.com/mozilla/airmozilla/blob/d9f559f7b75aca79818dcad8c281f956e22f6d24/airmozilla/main/models.py#L698
That keeps is simple and we don't have to worry about doing increments.
However, a problem is that you might have 1 event with N shortcodes (where N is >= 1).
For example, you decided to upload a different recording (e.g. one with some audio optimized for example). Now you might have had 1,000 views under the old Vid.ly video but 100 on the new Vid.ly video. It's still the same event. The true number should be 1,100. Not 100.
If we're going to allow for editing of videos we might end up, often, with many vid.ly submissions for 1 event so we need to solve the statistics issue.
| Reporter | ||
Comment 1•10 years ago
|
||
Two possible solutions:
A) Change all places where we use EventHitStats and use aggregates instead.
B) When we create a new EventHitStats record (where only the vidly shortcode is different), the carry the previous total_hits over somehow.
| Reporter | ||
Comment 2•10 years ago
|
||
Setting up a blocker on 1119986 because we have apparently let EventHitStats records be repeated that have the same event and shortcode.
Depends on: 1119986
Updated•10 years ago
|
Priority: -- → P1
| Reporter | ||
Updated•10 years ago
|
Priority: P1 → P2
Comment 3•4 years ago
|
||
Platform deprecated.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
Updated•4 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•