Ok, the patch is up and everything looks good. For the record, this was our fault because we were relying on a protected interface in the API. At the same time, it was triggered by a backend rollout; it might be nice to let us know these will be happening so we can watch our apps.
Thanks for the help! j On Apr 18, 4:21 pm, Alfred Fuller <arful...@google.com> wrote: > Ah, of course, the key word argument works, but keys_only queries have > never been compatible with multi-query. > > On Wed, Apr 18, 2012 at 3:04 PM, Jason Collins > <jason.a.coll...@gmail.com>wrote: > > > > > > > > > I am seeing this under 1.6.4. We had some conditional logic before, I > > will continue with that for now. Could be that this is supported under > > 1.6.5, but we're in an in-between stage at the moment... > > > BadRequestError: keys only queries are not supported by multi-query. > > > j > > > On Apr 18, 3:56 pm, Alfred Fuller <arful...@google.com> wrote: > > > Should work for everything, if not, let me know :-) > > > > On Wed, Apr 18, 2012 at 2:55 PM, Jason Collins < > > jason.a.coll...@gmail.com>wrote: > > > > > Will this work for MultiQuery too? > > > > j > > > > > On Apr 18, 3:50 pm, Alfred Fuller <arful...@google.com> wrote: > > > > > Is query a db.GqlQuery or a db.Query? > > > > > > In either case you can use: > > > > > > query.run(keys_only=True) # works for fetch and get as well > > > > > > On Wed, Apr 18, 2012 at 2:48 PM, Jason Collins < > > > > jason.a.coll...@gmail.com>wrote: > > > > > > > This is almost certainly due to a change in a protected attribute > > on > > > > > > the Query class in 1.6.5 (which is rolling out on this datacenter). > > > > > > > I KNOW, I KNOW - we should not be relying on a protected > > attribute. It > > > > > > was part of the global changes we needed to put in place for our > > HRD > > > > > > cutover. > > > > > > > So, that said, I need to convert a Query object into a > > keys_only=True > > > > > > Query object (i.e., everything else the same, but keys_only=True is > > > > > > set). Can anyone think of a safe way to do that? > > > > > > > (In 1.6.4, the following worked, which is now what is broken: > > > > > > "query._keys_only = True") > > > > > > > j > > > > > > > On Apr 18, 3:24 pm, Jason Collins <jason.a.coll...@gmail.com> > > wrote: > > > > > > > I don't think this is a datastore issue. The stack trace looks > > like a > > > > > > > python backend issue. > > > > > > > > On Apr 18, 3:09 pm, "powera (App Engine Reliablity)" > > > > > > > > <pow...@google.com> wrote: > > > > > > > > Nevermind, I can look up the enterprise support case. > > > > > > > > > On Apr 18, 2:07 pm, "powera (App Engine Reliablity)" > > > > > > > > > <pow...@google.com> wrote: > > > > > > > > > What is your app id? > > > > > > > > > > The admin console looks to have thrown higher error rates > > for a 5 > > > > > > > > > minute window recently, this is unrelated to any datastore > > > > issues. > > > > > > > > > > On Apr 18, 2:05 pm, Jason Collins <jason.a.coll...@gmail.com > > > > > wrote: > > > > > > > > > > > We are seeing this on data centre na3, but not on na6. > > > > > > > > > > > j > > > > > > > > > > > On Apr 18, 3:00 pm, Jason Collins < > > jason.a.coll...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > Also, deployments are throwing errors. > > > > > > > > > > > j > > > > > > > > > > > > On Apr 18, 2:55 pm, Jason Collins < > > jason.a.coll...@gmail.com > > > > > > > wrote: > > > > > > > > > > > > > Seeing lots of errors on db.get() suddenly and from all > > > > parts > > > > > > of our > > > > > > > > > > > > code (no, we haven't pushed any new code). > > > > > > > > > > > > > Also, our dashboard is throwing lots of errors. > > > > > > > > > > > > > Anyone else seeing this? (I've opened an enterprise > > support > > > > > > case > > > > > > > > > > > > already, but wondering if anyone else is seeing same.) > > > > > > > > > > > > > j > > > > > > > -- > > > > > > You received this message because you are subscribed to the Google > > > > Groups > > > > > > "Google App Engine" group. > > > > > > To post to this group, send email to > > google-appengine@googlegroups.com > > > > . > > > > > > To unsubscribe from this group, send email to > > > > > > google-appengine+unsubscr...@googlegroups.com. > > > > > > For more options, visit this group at > > > > > >http://groups.google.com/group/google-appengine?hl=en. > > > > > -- > > > > You received this message because you are subscribed to the Google > > Groups > > > > "Google App Engine" group. > > > > To post to this group, send email to google-appengine@googlegroups.com > > . > > > > To unsubscribe from this group, send email to > > > > google-appengine+unsubscr...@googlegroups.com. > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-appengine?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to google-appengine@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine+unsubscr...@googlegroups.com. > > For more options, visit this group at > >http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
