Closed Bug 1381734 Opened 7 years ago Closed 7 years ago

Add sync_engine_errors to hive metastore

Categories

(Data Platform and Tools :: General, enhancement)

Product:
Data Platform and Tools
Component:
General
Type:
enhancement
Priority:
Not set
Severity:
normal
Points:
1

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: markh, Unassigned)

References

Details

(Whiteboard: [SvcOps])

The sync_engine_errors dataset is a temporary table containing information about sync failures. The dataset lives in s3 at [1] and was generated via [2]. It should be named `sync_engine_errors`. This import is so we can evaluate the data - assuming it is OK, we'll then open another bug to have it scheduled. Please see bug 1349070 comment 2 for additional context. [1] s3://net-mozaws-prod-us-west-2-pipeline-analysis/tcsc/sync_engine_errors/v1/run_start_date=%s, where best I can tell from [2], start_date is 20170516 [2] https://gist.github.com/thomcc/5c1cb88eabc5897cd0fb32e0d928e02b
Points: --- → 1
Summary: Add churn_dev to hive metastore → Add sync_engine_errors to hive metastore
Please wait on this until the other bug is updated.
Depends on: 1349070
No longer depends on: 1349070
Is this still an active request? If so what is the priority?
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Component: Datasets: General → General
You need to log in before you can comment on or make changes to this bug.