Thanks, Chad. Re your comment about caching, I am using NDB on the Python side, which I thought used memcache automatically. So I guess I am using caching, but I thought that modules in the same project (mine are) shared memcache. Is that not true if one module is Python and the other Java?
On Monday, October 31, 2016 at 3:07:43 PM UTC-4, Chad Vincent wrote: > > Also, make sure you aren't doing deferred writes or starting the Java > request before your Python transaction closes. > > On Monday, October 31, 2016 at 2:05:06 PM UTC-5, Chad Vincent wrote: >> >> Yes. Consistency is handled by the database layer, not the application >> runtime. >> >> HOWEVER, if you are caching entities (Objectify, etc.) you either need to >> ensure your Memcache keys are identical or disable caching for those >> entities. Otherwise the Java cache may return a stale result because the >> Python module didn't clear/update the entity on write. >> >> On Monday, October 31, 2016 at 8:41:07 AM UTC-5, Jonathan Munson wrote: >>> >>> Hi, >>> >>> We have an app wherein a Datastore entity is written to by a Python >>> module (using NDB), and then in an immediately following request, read >>> from, using the entity's key, by a Java module. In a situation where the >>> app was heavily loaded, it seemed like the Java module was reading stale >>> data. The Datastore documentation says that lookup-by-key requests are >>> strongly consistent, but does that apply even when writes are from a Python >>> module and reads are from a Java module? >>> >>> Thanks, >>> >>> --Jon >>> >> -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. 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/3d0c204d-f2d4-4cb7-8db0-26c9db942e6a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
