ah, so you can't bury something that's not ready yet?
--chad

On Wed, Aug 10, 2011 at 10:29 PM, Daniel Olfelt <[email protected]> wrote:

> Yeah, I thought that would work, but bury works on the same objects that
> delete does. I do know the ID of the job I am trying to delete from the
> delay queue, but when I try to delete it, even though I know it is in the
> queue, it returns NOT_FOUND.
>
> --Daniel
>
> On Wed, Aug 10, 2011 at 7:46 PM, Chad Kouse <[email protected]> wrote:
>
>> From reading the protocol doc - maybe you could work around it if you know
>> the id. You might be able to bury and then delete the job. Not sure.
>>
>> --chad
>>
>> On Aug 10, 2011, at 8:21 PM, Daniel Olfelt <[email protected]> wrote:
>>
>> How hard would it be to add deleting of delayed jobs? Is there a reason it
>> isn't an option? If it's just time, I might consider trying my hand at
>> adding it.
>>
>> --Daniel
>> On Aug 10, 2011 4:46 PM, "Chad Kouse" < <[email protected]>
>> [email protected]> wrote:
>> > Nothing I can think of that's too elegant. You could use memcached
>> > though and stick a record in there relating to the delayed job. Then
>> > when you want to delete the job just delete the associated memcached
>> > object. And when you are consuming jobs check for the associated
>> > record in memcached first.
>> >
>> > --chad
>> >
>> > On Aug 10, 2011, at 5:25 PM, Daniel < <[email protected]>
>> [email protected]> wrote:
>> >
>> >> Is there any way to delete a delayed job, or modify a delayed job? I
>> >> am trying to run several commands several minutes after user action,
>> >> but if there is a duplicate job in delay, I do not want it to run
>> >> twice.
>> >>
>> >> I know beanstalkd does not support deleting delayed jobs currently,
>> >> but is there any sort of work around?
>> >>
>> >> - Daniel
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> Groups "beanstalk-talk" group.
>> >> To post to this group, send email to <[email protected]>
>> [email protected].
>> >> To unsubscribe from this group, send email to
>> <beanstalk-talk%[email protected]>
>> [email protected].
>> >> For more options, visit this group at
>> <http://groups.google.com/group/beanstalk-talk?hl=en>
>> http://groups.google.com/group/beanstalk-talk?hl=en.
>> >>
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "beanstalk-talk" group.
>> > To post to this group, send email to <[email protected]>
>> [email protected].
>> > To unsubscribe from this group, send email to
>> <beanstalk-talk%[email protected]>
>> [email protected].
>> > For more options, visit this group at
>> <http://groups.google.com/group/beanstalk-talk?hl=en>
>> http://groups.google.com/group/beanstalk-talk?hl=en.
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "beanstalk-talk" group.
>> 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.
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "beanstalk-talk" group.
>> 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.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "beanstalk-talk" group.
> 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.
>

-- 
You received this message because you are subscribed to the Google Groups 
"beanstalk-talk" group.
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.

Reply via email to