[google-appengine] Re: I update an entity, then reading with Request Factory I sometimes get the old value - High Replication Datastore (HRD)

As you pointed out, to guarantee strong consistency you need to use an Ancestor query, or retrieve an Entity by its Key value. In both cases, the data store should roll-forward any commits that have not yet been applied. I am a little confused because it *looks *like you are retrieving the Enti

[google-appengine] Re: I update an entity, then reading with Request Factory I sometimes get the old value - High Replication Datastore (HRD)

Michael, thank you for your comment. Thus, the only way to make a strongly consistent update (no Ancestor Entity scenario) is after the update to retrieve the entity by its key value. This way all pending changes will be roll-forwarded, then read again using Request Factory from client side (e.g.