Closed
Bug 1393144
Opened 8 years ago
Closed 7 years ago
error_aggregates should use submission_date_s3 partitioning
Categories
(Data Platform and Tools Graveyard :: Datasets: Error Aggregates, enhancement, P1)
Data Platform and Tools Graveyard
Datasets: Error Aggregates
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: frank, Assigned: akomar)
References
Details
Attachments
(1 file)
We have largely aligned on partitioning by submission_date_s3, not submission_date. Along with that, the date format should be 'YYYYMMDD', rather than 'YYYY-MM-DD'.
Reporter | ||
Comment 1•7 years ago
|
||
Old data will need to be moved.
Points: --- → 3
Component: Mission Control → Datasets: Error Aggregates
Priority: -- → P3
Product: Cloud Services → Data Platform and Tools
Assignee | ||
Comment 2•7 years ago
|
||
:frank Batch mode already uses submission_date_s3, whereas streaming one writes submission date.
I think we should standardize this before going live with v2 (as backfilling isn't straightforward now).
However, I don't quite get the meaning of submission_date_s3 in case of a streaming job - after all, data it's processing doesn't go through s3, does it?
Flags: needinfo?(fbertsch)
Reporter | ||
Comment 3•7 years ago
|
||
(In reply to akomarzewski from comment #2)
> :frank Batch mode already uses submission_date_s3, whereas streaming one
> writes submission date.
> I think we should standardize this before going live with v2 (as backfilling
> isn't straightforward now).
Yes that should definitely be rectified
> However, I don't quite get the meaning of submission_date_s3 in case of a
> streaming job - after all, data it's processing doesn't go through s3, does
> it?
True. `submission_date_s3` started being our default for submission-date based partitions, mainly because it says something about the partition existing in s3. There's no real formality behind it other than convention.
Flags: needinfo?(fbertsch)
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → akomarzewski
Assignee | ||
Updated•7 years ago
|
Priority: P3 → P1
Comment 4•7 years ago
|
||
Assignee | ||
Comment 5•7 years ago
|
||
Will: FYI. I noticed missioncontrol uses submission_date, so this change probably has to be taken into account there.
Flags: needinfo?(wlachance)
Comment 6•7 years ago
|
||
(In reply to akomarzewski from comment #5)
> Will: FYI. I noticed missioncontrol uses submission_date, so this change
> probably has to be taken into account there.
Yup, it's on my radar!
Flags: needinfo?(wlachance)
Assignee | ||
Updated•7 years ago
|
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
•