On Friday, 16 August 2013 07:21:21 UTC+12, Alexis wrote:
>
> There is currently no way to target a specific version on a non-default
> module using cron.yaml or dispatch.yaml.
> But that may work programmatically (when you enqueue the task you can also
> specify a target, and maybe "version.modul
I tested queue with target parameter directing to non default module.
Unfortunately I tested it on production as it seemed to work.
I routed certain messages and after about a day when checking stats I found
out that about 1/4 of the messages were lost.
Removing the target from the queue and ha
It works for me.
The "target" parameter of a cron job definition currently will go to the
default version of the specified module or the specified version of the
default module.
If you both have a URL for the Cron job that points to an specific module
and a "target" parameter that points differ
For some reason target works for me both in queue and cron... so it looks
to be supported feature..
четверг, 15 августа 2013 г., 8:38:48 UTC+3 пользователь Vinny P написал:
>
> On Wed, Aug 14, 2013 at 9:34 AM, bFlood
>
> > wrote:
>
>> hello all
>>
>> I'm having trouble targeting specific Module
On Wed, Aug 14, 2013 at 9:34 AM, bFlood wrote:
> hello all
>
> I'm having trouble targeting specific Modules from the Task queue, I
> thought it would be as simple as Backends using the "target" param. Am I
> missing something obvious?
>
Use a dispatch file. See
https://developers.google.com/ap
hello all
I'm having trouble targeting specific Modules from the Task queue, I
thought it would be as simple as Backends using the "target" param. Am I
missing something obvious?
ex:
taskqueue.add(queue_name='backup', url="/tasks/backup", params=params,
target="worker")
where worker is the na
