Closed
Bug 1355790
Opened 8 years ago
Closed 8 years ago
remove or rename the "main_summary_20161030" table in hive
Categories
(Data Platform and Tools :: General, defect, P1)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mreid, Assigned: robotblake)
Details
(Whiteboard: [SvcOps])
This table is now the default table when you SELECT from "main_summary" (presumably since it has the highest version).
The expected default table should be main_summary_v3.
STR:
SELECT COUNT(*) FROM main_summary WHERE submission_date_s3 = '20170410' AND sample_id = '10'
# returns 0
SELECT COUNT(*) FROM main_summary_v3 WHERE submission_date_s3 = '20170410' AND sample_id = '10'
# returns more than 0
Updated•8 years ago
|
Assignee: nobody → fbertsch
Comment 1•8 years ago
|
||
Current tables are fixed. Cron job doesn't include this table, so it doesn't look like it should be a problem. If it comes up again we can take another look.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 2•8 years ago
|
||
A table called 'default.main_summary_20161030_v3' is still (or again?) showing up in re:dash and acting as the default "main_summary" table.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 3•8 years ago
|
||
Do we know what's causing this?
Comment 4•8 years ago
|
||
(In reply to Roberto Agostino Vitillo (:rvitillo) from comment #3)
> Do we know what's causing this?
Apparently sunahsuh was testing some dataset. We're rerunning right now. I think we should add an option to p2h where it doesn't set the non-versioned table.
Updated•8 years ago
|
Component: Metrics: Pipeline → Datasets: Main Summary
Product: Cloud Services → Data Platform and Tools
Updated•8 years ago
|
Assignee: fbertsch → bimsland
Priority: -- → P1
Whiteboard: [SvcOps]
| Assignee | ||
Comment 5•8 years ago
|
||
The table has been deleted.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Component: Datasets: Main Summary → General
You need to log in
before you can comment on or make changes to this bug.
Description
•