On Mon, Oct 31, 2011 at 7:01 PM, Aswath Satrasala < aswath.satras...@gmail.com> wrote:
> Hi, > I am trying HRD on local dev server. I have bunch of webdriver tests for > different parts of my application that create entities and then doing a > list of all the entities. > My tests are failing in several places. It is due to the eventual > consistency of the HRD. The tests run fine on M/S and on both > production/local environment. > I have 20-30 KINDS, and entities are created for 1-or more KINDs depending > on the business logic, all in a transaction. Immediately, various reports > are done. They fail. > > My question: What pattern needs to be followed? My application has grown > very large during last 1.5 years or so. Doing re-factoring at every place > in the application for eventual consistency will be a very large effort for > a small team. I don't even know what extra work needs to be put to get this > fixed. > > Am I better of sticking with M/S. So far, I have managed and designed > entity relationships to work within one entity group. I mean, for a given business logic, i create group of entities involving different KINDS, all with same Parentkey. The parentKey itself is based it on the Customer/supplier in the given context. Hence, my queries/reports are spread across different entity groups. > > > Are there any patterns coming out from the Objectify team to handle > Eventual consistency issue of the HRD? > > -Aswath > www.AccountingGuru.in > -- 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.
