Closed Bug 1427749 Opened 8 years ago Closed 8 years ago

Longitudinal hasn't updated since 2017-12-09

Categories

(Data Platform and Tools Graveyard :: Datasets: Longitudinal, defect)

Product:
Data Platform and Tools Graveyard
Component:
Datasets: Longitudinal
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: chutten, Unassigned)

References

Details

Might be a dupe of bug 1404912 given that :mreid (who's supposed to be on PTO) saw that it timed out. And then it hit bug 1404715, so it's in a bit of a pickle. :RyanVM was asking after it on #telemetry today, but he's okay to wait a bit for people to trickle back from PTO.
Blocks: 1427547
I have a PR awaiting review here: https://github.com/mozilla/telemetry-batch-view/pull/362 Once that's merged I'll run the latest date (20171230) and if that goes well I'll make sure to backfill the dates in bug 1427547
v20171230 ran successfully and preliminary checks look good -- I'm going to re-run v20171223 and v20171217 now, and we should be able to close this out by the end of the day.
Longitudinal v20171230, v20171223, and v20171217 are complete and queryable from both the Presto and Athena sources in STMO. Unfortunately I found a potential duplicate data in v20171209 and possibly a few other dates while I was verifying these runs, which I'll file a separate bug about :(
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
(In reply to Sunah Suh (she/her) [:sunahsuh] from comment #3) > Longitudinal v20171230, v20171223, and v20171217 are complete and queryable > from both the Presto and Athena sources in STMO. > > Unfortunately I found a potential duplicate data in v20171209 and possibly a > few other dates while I was verifying these runs, which I'll file a separate > bug about :( Could you please cc me to that bug?
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.