[google-appengine] Re: High untraced time on lightweight endpoint

2019-05-18 Thread Jeremy D
As you can see in the screenshot, this was not a request that spawned a new instance. Memory usage also doesn't appear to be a factor here. On Thursday, May 16, 2019 at 2:29:36 PM UTC-5, Aref Amiri (Cloud Platform Support) wrote: > > Long Untraced >

[google-appengine] Re: DataStore Key handling

2019-05-18 Thread 'George (Cloud Platform Support)' via Google App Engine
Hello Tony, Each entity in Datastore has a key that uniquely identifies it. The key consists of the following components: - The namespace of the entity, which allows for multitenancy - The kind of the entity, which categorizes it for the purpose of queries - An identifier for the individual ent

[google-appengine] Re: java.lang.outofmemoryerror: java heap space when creating ZIP archives in Google App Engine ( Java)

2019-05-18 Thread 'George (Cloud Platform Support)' via Google App Engine
Hello Ibrahim, Which version of Java do you use? To avoid out-of-memory errors, you may consider setting a higher instance class in the appengine-web.xml configuration file, using . If you use Java 8, you could ask for more memory in the same configuration file, by means of:

[google-appengine] Re: Broken: Deployment using service accounts

2019-05-18 Thread 'George (Cloud Platform Support)' via Google App Engine
If you refer to the "Predefined App Engine roles" sub-chapter of the "Access Control" online document, you'll notice that only the App Engine Deployer role has "Write access only to deploy and c

[google-appengine] Re: Changing StringProperty to TextProperty of existing AppEngine DataStore entity without losing data

2019-05-18 Thread Vitaly Bogomolov
Hi. The key thing is usage an Expando subclass. For example, as described here: Change IntegerProperty to FloatProperty of existing AppEngine DataStore https://stackoverflow.com/questions/4742875/change-integerproperty-to-floatproperty-of-existing-appengine-datastore Also, these links may be use