Hey Faried, As Tim H suggested, this is likely due to eventual consistency. Datastore has an eventual-consistency model of replication which allows it to be highly-available and scalable while making a slight trade-off on the ability to get the latest copy of entities at every given moment. You can, however, use the key of an entity to retrieve it immediately, if it exists anywhere in the system, as opposed to a regular "get" query, which can show old results (including results where the entity doesn't exist yet). I suggest replacing your "get" query with a "get-by-key" query to force strong consistency. You can read more about Datastore and consistency in the documentation <https://cloud.google.com/datastore/docs/articles/balancing-strong-and-eventual-consistency-with-google-cloud-datastore/#additional-resources> .
Cheers, Nick Cloud Platform Community Support On Wednesday, June 8, 2016 at 6:31:32 AM UTC-4, Faried Nawaz wrote: > > On Wed, Jun 8, 2016 at 2:46 PM, timh <[email protected]> wrote: > > Are you getting that data via a query or via key using get, > > If you are using a query then you will need to start reading up on > Eventual > > consistancy > > It's a "get". I just need some way to flush the cached data without > putting "use_memcache=False" everywhere. > > It's an issue I don't run into if all my code runs under the Python > service. It can't do that in this case, since file uploads can take > longer than 60 seconds. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/f4e2a33f-d6c5-4012-b73a-f06e5c96f951%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
