What's the logic about search? about beanstalk_console HOT 7 CLOSED

yep that needs to be updated
I am travelling for 2 weeks, will see when I have time to do a pull request

from beanstalk_console.

If you want I can do it but the problem is: how?
How can we know what's the maximum ID to search for? The stats-tube command doesn't have this information. Any idea?

from beanstalk_console.

as far I know there is no way to obtain the last job id, as the queue doesn't expose it.
we need to loop all jobs until we reach one limit

• eg the maximum number of jobs to return eg: 20 results
• or we have fetched total number of jobs that exists on the tube itself

this last one could also mean that if some other tube has 1 million message, they will be peaked.
we could also introduce another two factors

• total system jobs to check eg: 10 000
• or total number of seconds allowed to fetch for jobs eg: 30 seconds

what do you think?

from beanstalk_console.

Yes I agree.
There is no elegant way to it because the beanstalkd tube is not "inspectable" by design. I'll try to provide a PR for this.

from beanstalk_console.

@pentium10 look at the #162, what do you think?

from beanstalk_console.

from beanstalk_console.

It was already limited when I started to work on this. There was two kind of limits:

• It stops when it find 25 jobs
• Or it stops after 25 seconds

So if you have to many jobs it lasts for maximum 25 seconds.

from beanstalk_console.