I have a question regarding the HRD emulation in the java dev app server. I perform the following operations from a web app, so they're within requests:
request 1. - 'get' entity - (modify entity) - 'put' entity * 'get' entity request 2. - query entity I expect to see inconsistent data in the request 2 query, but don't. - It doesn't matter what the 'high rep job policy unassigned pct' value is set to the data is always consistent. The 'expected' behaviour, occasional inconsistency data in the query, occurs when the 'get' marked with the * is removed. - Without the preceding 'get' I immediately see inconsistent data in the query. I'm wondering if this is an issue with the dev-app servers emulation of eventual consistency? - In the example, once query 2 does return inconsistent data, it's inconsistent for roughly 20 seconds - is this normal for the dev-app server? (I assume it's worst case). - Checking the datastore's admin console during this ~20 second period will immediately cause the query to return consistent data. To conclude: It seems that issuing at 'get' operation, whilst data is inconsistent, forces the dev-app server to return consistent data for any subsequent queries, (masking the HR behaviour). Is this an issue or my flawed understanding of the HR behaviour? - Does a 'get' really cause a queries containing a recently 'put' entities to return consistently. GAE 1.5.3 (OSX 10.7.1,Java 1.6.0_26) -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
