Due to various cases I'd like to bury a job during its work cycle. To retrieve the reason why a job has been buried I would like to append some data (all the data is JSON encoded).
Is there some way to get this done? The only method I can come up with now is to delete the job being worked on, create a clone of the job, add the new data, put that in the queue again and bury it directly. This seems a bit odd with a lot of steps. Is there anything I miss in this picture? The same question applies to releasing jobs during the work cycle, since I can't imagine something different here too. I have two examples where above requirements are shown: 1. When a job notifies the worker it must be buried, the buried state is different from the job throwing an exception during execution. So I would likely add a "buried_type" to the job; 2. A job can connect to an external 3rd party service. When a time-out happens, the job must be released and rerun after a delay. When the job is retried for x times, I want to bury it for user inspection. --- Jurian Sluiman -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/beanstalk-talk/-/-1Yju7rDnagJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
