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 handling the messages by the default module fixed this back to normal. I don't know whats wrong, but there is something wrong definitely...
четверг, 15 августа 2013 г., 22:21:21 UTC+3 пользователь Alexis написал: > > 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 differently, the URL forwarding rule > via dispatch.yaml will prevail here. > > 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.module" works) > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
