The High Replication Datastore is the name for the current Datastore, as opposed to the old Datastore which was called Master / Slave <http://googleappengine.blogspot.com/2012/04/masterslave-datastore-thanks-for-all.html>.
On Friday, May 20, 2016 at 5:59:20 AM UTC-4, Anastasios Hatzis wrote: > > Hi everyone! > > While debugging the datastore behavior for a local unit test, I returned > to the docs. > > On this page: > > https://cloud.google.com/appengine/docs/python/tools/localunittesting > > there is a section about testing Datastore, followed by a separate section > about testing High Replication Datastore. It was my understanding that HRD > is just the old name of the Google Cloud Datastore, but the docs looks as > if it were two separate things. > > If the consistency policy is the only difference (the code suggests so), I > would like to know what's the benefit to test with for example > > > *self.testbed.init_datastore_v3_stub(consistency_policy=datastore_stub_util.PseudoRandomHRConsistencyPolicy(probability=0) > > * > (or 0.5, 1 etc.) > > I understand the difference between strong consistency and eventual > consistency, and that I can't run ancestor-less queries inside > transactions, but I don't understand why I would test for eventual > consistency. Maybe I have blackout here. > > Ani > -- 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/80956b39-2477-4725-abe1-c2ef7a088c21%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
