-
Notifications
You must be signed in to change notification settings - Fork 159
Feat; job_queue table definition & mark a request as complete if all jobs are finished #2200
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
Feat; job_queue table definition & mark a request as complete if all jobs are finished #2200
Conversation
3e1489a
to
d0ed82f
Compare
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.
Did a quick scan and left a bunch of comments, but it would likely be best to discuss this at our call.
1 | ||
FROM | ||
job_queue | ||
WHERE job_queue.request_id = benchmark_request.id |
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.
Once we also add the parent benchmark tag here, could you please run EXPLAIN
to make sure that the jobs (not requests) are looked up by index? Also would be nice to check if requests are accessed by index.
…jobs are finished
…benchmark set made into a a struct
f7f9747
to
eb422a5
Compare
Superseded by; #2214 |
job_queue
table.job_queue
.benchmark_request
as complete if all jobs associated with the request have the status ofsuccess
orfailure
.I've omitted
job_splitting
as this PR is modestly big. However, bar marking things as complete, the PR is fairly mechanical.