[google-appengine] Re: appengine TimeZone changed

Thank you for the information. But my question is - why it is showing the different time zone in servlets and filters, even when we are setting the default time zone to GMT+00:00. The issue is with the local development server. But in the production server it is fine. On Monday, March 6, 2017 a

[google-appengine] Re: Datastore queries are unpredictably slow when a limit is applied

Datastore query times are not guaranteed to be consistent, as Datastore is a shared, distributed service. Since you're performing 4 equality filters this can add to the variation. The question of how to optimize for speed is a bit broad and depends on your data model. With that being said I can

[google-appengine] Re: Is cron.yaml supported with custom runtimes?

The docs do suggest that cron.yaml should work on the OpenJDK runtime. I'll investigate this more and update the thread once I've finished testing. On Sunday, March 5, 2017 at 4:03:23 AM UTC-5, Ben Rometsch wrote: > > Hmm I

[google-appengine] Meet today or tomorrow at Next17

I am in the Marriot in SF involved with bootcamps today and tomorrow. If anybody is around interested in meeting at the end of the day for a drink, send me a direct e-mail. PK p...@gae123.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" grou

[google-appengine] Re: How to download data from my datastore to the local machine

Glad to hear that you’ve made it work, as the Remote API may in fact require additional setup according to your environment. Nevertheless, I would recommend another alternative potentially easier to configure for accessing the Datastore in the future. The alternative consists in using the Pyt

[google-appengine] Re: Google App Engine multiple regions

Hey Pavelescu, The page you link, "Creating Cross-Region Load Balancing", from our docs, is relevant for Compute Engine instances, rather than App Engine. While App Engine Flexible Environment apps run on Compute Engine VM's, they deploy only to the same region that you select for your App Engi

[google-appengine] Re: Search API: How to prevent the 2000 bytes query limit?

Hello Jonas, You may consider narrowing the range before sorting, and other similar tricks, to improve efficiency. It may be worthwhile checking the "Search Best Practices" document . Also, general information is

Re: [google-appengine] Re: Life beyond compat

The Memcache service is currently not available for the App Engine flexible environment, as mentioned in the "Upgrading to the Latest App Engine Flexible Environment Beta Release" document . If your code contains calls to memcache

[google-appengine] Search API: How to prevent the 2000 bytes query limit?

We are using the GAE Search API since quite some time but recently hit the query limit of 2000 bytes: > > java.lang.IllegalArgumentException: query string must not be longer than > 2000 bytes, was 2384 We're basically having documents saved with a secondary id set as an atomic field. Within o

[google-appengine] Composite index - ZigZag Merge

Hi, I have the following ofy class class Job { @Id Long id; @Index String tenantId; @Index long partyOrgId; @Index long seqId } ofy.query.filter("tenantId", tenantId).filter("partyOrgId", partyOrgId).sort("-seqId").first().now(); The above query throws an composite needed index