Good idea, Chad. Thanks!
On Monday, July 1, 2013 3:47:04 PM UTC-5, chadkouse wrote: > > Include the job history that you care about in the updated payload. > That's the best way. > — > chad > > > On Mon, Jul 1, 2013 at 4:38 PM, Aaron <[email protected] <javascript:>>wrote: > >> Is there a way to release a job with an updated data payload? I want to >> create jobs that run until they have a problem and then get released to be >> tried again at a later time. However, they also perform their work in >> incremental steps (i.e. quanta) so I want to update the job's data payload >> with successfully created data when I release. This way, the next time the >> job runs, it doesn't have to duplicate a quanta of work that has >> successfully completed in a previous run. >> >> I could just delete the job and create a new one with the updated data, >> but then I loose all of the job history that beanstalk provides. :^( >> >> Any ideas? >> >> Thanks! >> - Aaron >> >> -- >> You received this message because you are subscribed to the Google Groups >> "beanstalk-talk" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected]<javascript:> >> . >> Visit this group at http://groups.google.com/group/beanstalk-talk. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/beanstalk-talk. For more options, visit https://groups.google.com/groups/opt_out.
