I would take a look at this article <https://cloud.google.com/appengine/docs/java/datastore/jdo/queries>, specifically the second paragraph under 'Datastore Read Policy and Call Deadline'.:
' If the query uses an ancestor filter, you can use transactions <https://cloud.google.com/appengine/docs/java/datastore/transactions> to ensure a consistent result set.) See the article Transaction Isolation in App Engine <https://cloud.google.com/appengine/articles/transaction_isolation> for more information on how entities and indexes are updated. ' On Saturday, August 1, 2015 at 6:24:55 PM UTC-4, Thomas Becker wrote: > > I am using the app engine datastore with Java JDO. According to the > documentation, ancestor queries are always strongly consistent. Recently, > however, I've been seeing a lot of stale data from ancestor queries. It > seems to happen randomly. A query may return the most recent data, and a > moment later, the same query returns stale data. > -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/a672af3b-5de7-472c-9fe0-0d61521e8928%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
