Does your node service use NDB or DB? if it is using NDB then NDB takes care of flushing the cache for you when you update an object, but you have to `get_by_key` in order to get the latest copy.
On Wednesday, June 8, 2016 at 1:33:15 AM UTC-7, Faried Nawaz wrote: > > Hello, > > I have a Python application deployed as my App Engine project's default > service. I also have a node service deployed in the same project for > long-running tasks (uploads of large files to GCS). After a file is > uploaded, the node code updates an existing Datastore object with the path > to the file on GCS. > > I've noticed that if I fetch the object from the Python service after the > update, I don't always get the latest data. Other than by sprinkling > use_cache=False, > use_memcache=False in a bunch of places on the Python side (and taking a > performance hit), how can I work around this problem? Is there any way for > the node service to flush or update the object in memcache? I use ndb on > the Python side. > > > Faried. > -- 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/0a71de1c-b14d-4d5c-a01b-2fb6cfd69ca9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
