-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(warehouse): use first_event_at while pickup for warehouse processing jobs #3036
Conversation
Codecov ReportBase: 52.97% // Head: 53.12% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #3036 +/- ##
==========================================
+ Coverage 52.97% 53.12% +0.14%
==========================================
Files 334 334
Lines 51863 51858 -5
==========================================
+ Hits 27475 27548 +73
+ Misses 22785 22707 -78
Partials 1603 1603
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@@ -263,7 +264,7 @@ func (uploads *Uploads) GetToProcess(ctx context.Context, destType string, limit | |||
grouped_uploads.row_number = 1 | |||
ORDER BY | |||
COALESCE(metadata->>'priority', '100')::int ASC, | |||
id ASC | |||
COALESCE(first_event_at, NOW()) ASC |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It shouldn't be complex to write a test for first_event_at
behaviour.
Hey @lvrach merged this without checking the comment. @achettyiitr will add the test in another PR sorry for the trouble |
Description
Use first_event_at while pickup for warehouse processing jobs
Notion Ticket
https://www.notion.so/rudderstacks/Use-first_event_at-while-pickup-from-processing-31c841fcdecc4ea8b6139ee0cb4d8daa?pvs=4
Security