Tom Gibara <tomgib...@gmail.com> Mar 22 08:12PM wrote: > Thanks for the link, somehow I'd managed to miss that page of > documentation entirely*; it's good to know, though it indicates other > problems for the OP. > > I'm not clear on why eventually consistent gets aren't an option, ie. > why all gets are indicated as being strongly consistent.
You can get eventually-consistent gets with the HR datastore if you create a DatastoreServiceConfig with myPolicy = DatastoreServiceConfig.withReadPolicy(ReadPolicy.Consistency.EVENTUAL) and use that policy when creating your datastore service (i.e., the same way you get eventually consistent gets with the master-slave datastore). -- David Gay - AppEngine d...@google.com -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
