2 ms·
Does it do job completion notification? Along the lines of: _, err := river.Execute(context.Background(), j) // Enqueue the job, and wait for completion
by justinclift 3y ago
Does it do job completion notification?
Along the lines of:
_, err := river.Execute(context.Background(), j) // Enqueue the job, and wait for completion
if err != nil {
log.Fatalf("Unable to execute job: %s", err)
}
log.Printf("Job completed")
Does that make sense?
- bgentry 3y agoIt sounds like you're looking to be able to find out when a job has finished working, no matter which node it was run on. No, River does not have a mechanism for that today. It's definitely something we've talked about though.
- justinclift 3y agoThanks. Yeah, that's definitely a requirement of the queueing systems I'm working with. It's effectively "run this remote function, and return when you have the result data". Fan-out RPC (-ish) style stuff, rather than async "queue an email for sending later".